Issue Details (XML | Word | Printable)

Key: ADFEMG-70
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Jan Vervecken
Votes: 0
Watchers: 0
Operations

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

ER 15841916 : IDE TO INFORM FUTURE APPS VERSION NUMBER

Created: 08/Nov/12 08:00 PM   Updated: 16/Aug/13 01:29 AM   Resolved: 16/Aug/13 01:29 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags:
Participants: chriscmuir and Jan Vervecken


 Description  « Hide

creating a separate ADFEMG JIRA issue, copying the comment
at http://java.net/jira/browse/ADFEMG-34?focusedCommentId=349626&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_349626

As extension to bugs 13402635/14843385 I've raised ER 15841916 stating:

@ This ER relates to base bug 14843385 and relating bug 13402635.
@ .
@ The basis of base bug 14843385 is:
@ .
@ "We're getting a number of bugs logged, mostly with ClassNotFoundExceptions,
@ from 11.1.1.6 and 11.1.2 because users are able to open applications created
@ in later versions of jdev in those builds. If possible, this should be fixed
@ on all active branches."
@ .
@ As relating to this issue once fixed, is even if we do block this scenario,
@ we then leave the user without knowing what version of JDev their future
@ application came from. This may leaving them guessing which JDeveloper
@ release to use.
@ .
@ The solution is on blocking the user from opening the future application in
@ an older JDev release, is we should also inform them what version of
@ JDeveloper the application has come from.

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, 11.1.1.6.0 and 11.1.2.3.0.
@ As such it's an easy mistake to attempt to open source code against the wrong
@ version of ojdeploy, and we should provide not only protection from doing
@ this, but also advice to the developer which JDeveloper version they should
@ be using for the source code.




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

No progress on this ER, sent internal email to give ER a poke.

CM.


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

In speaking to the developers this has already been implemented in 12.1.2. On opening a application from a future JDev version (say JDev 12.1.3) the user will see the following warning message:

"Unable to load the application file.Workspace TestLOVAutoSuggest.jws already migrated to newer version (12.1.3.0.0)."

Will leave this for review, and next time I revisit the ADF EMG issues there has been no comments I'll close this issue.

CM.


chriscmuir added a comment - 16/Aug/13 01:29 AM

As per last issue update, issue closed.

CM.