Issue Details (XML | Word | Printable)

Key: ADFEMG-71
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Jan Vervecken
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.


Created: 08/Nov/12 08:02 PM   Updated: 05/Nov/13 02:06 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: chriscmuir and Jan Vervecken

 Description  « Hide

creating a separate ADFEMG JIRA issue, copying the comment

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.

Business justification:

@ 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, and
@ 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.

Jan Vervecken added a comment - 08/Nov/12 08:02 PM


Currently I am unable to find enhancement request 15841961 on My Oracle Support.
Has ER 15841961 been published?

Jan Vervecken

chriscmuir added a comment - 09/Nov/12 02:46 AM

Apologies, should be fixed.

Jan Vervecken added a comment - 12/Nov/12 09:39 PM

Thank you for the update Chris.

On My Oracle Support I have now been able to find enhancement request 15841961, "MIGRATION WIZARD TO INFORM USER WHICH VERSION OF JDEV APPS COMES FROM".

Jan Vervecken

chriscmuir added a comment - 15/Jul/13 04:42 AM

No progress on ER. Sent email internally to give this ER a poke.


chriscmuir added a comment - 19/Jul/13 05:12 PM

Though not officially scheduled, via discussions devs are considering to place this in the 12.1.3 build.


chriscmuir added a comment - 05/Nov/13 02:06 AM

Sent internal "bump" as there hasn't been update for sometime.