As separate to ER 15841916, I've also lodged ER 15841961 for the migration wizard to report the JDev version number the application is coming from:
@ This ER is the exact opposite to ER 15841916.
@ In ER 15841916 the issue is about developers taking ADF applications and
@ opening them in previous versions of JDeveloper. As per bugs
@ 14843385/13402635 we want to stop the developer doing this. ER 15841916
@ takes this one step further by suggesting we should also tell the user which
@ version of JDeveloper the source code came from so they then know which
@ JDeveloper version to open and edit the source code.
@ In context of this ER, it's also possible to take applications written in an
@ older version of ADF and open them in a future version of JDeveloper, which
@ typically kicks off the migration wizard. In some cases it might be
@ undesirable for the developer to do this as they may have mistankly opened
@ the application in the wrong JDeveloper version. However like the other ER
@ we don't currently provide any information on what version of JDeveloper the
@ source code has come from, leaving the developer to guess this.
@ As such ER requests that the migration wizard includes a visual indication of
@ which version of JDeveloper the source code came from to assist the developer
@ in solving this issue.
@ Many customers are now developing with multiple versions of JDeveloper at the
@ same time. For example customers who use FMW products and ADF Mobile
@ currently would be using two versions of the IDE, 126.96.36.199.0 and 188.8.131.52.0.
@ As such it's an easy mistake to attempt to open source code against the wrong
@ version of JDev, and we should provide not only friendly warnings that we're
@ about to upgrade the source code and give them the chance to back out, but
@ also give advise to the developer which JDeveloper version they should be
@ using for the source code if they decide to exist the migration process.