Sara Tracy wrote:I don't think there is backward compatibility in JDeveloper, hence my applications might throw errors in a higher version of JDeveloper.
It's true that the JDev project files are version specific. In my experience, when you install a newer version, it asks you whether you'd like to migrate existing project files to the newer file format. I believe this prompt also occurs whenever you try to open workspace created by an earlier version.
I haven't tried to make the leap all the way from 10.1.2 to current in one move, so I'm not sure how effective that migration is. You could always back up your files and then try it out!
As for the jdk, there are two issues: which jdk is bundled and which is referenced in a project. These need not be the same.
In general, code written to an older jdk will run on a newer, but not necessarily vice versa. So your app written to 1.4.x can probably be compiled to 1.6 (and would probably benefit from refactoring to take advantage of new language features).
So if I have both JDev 10.1.2 and JDev 11.x.x, can I have the latest JDK version on my machine?
Yes, you can have multiple jdk instances in different versions on your machine, and you can associate a particular jdk with a particular project.
I read in the JDev 10.1.2 documentation, that I'm required to have JDK 1.4 if I need to work on JDev 10.1.2.
I think that's a minimum, not a peg.