creating a separate ADFEMG JIRA issue, copying the comment
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 220.127.116.11 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.
@ 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, 18.104.22.168.0 and 22.214.171.124.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.