Currently, JDO does not use any java API beyond 1.5, so it compiles
and would run using old, obsolete jvms.
I think that without a lot more discussion on the user list, we
shouldn’t change the required jvm level.
Many libraries have already changed to 1.7 minimum, including various
Apache (inc Apache ISIS, which provides JDO persistence).
Since it has been a while since 1.7 came out, and Oracle no longer
supports 1.5, I’d be happy if we discussed changing the minimum level
to 1.6.
Oracle will no longer support 1.6 soon, no? (let's not count the people
paying ;-)
So the real issue is DataNucleus. Is there a need for DataNucleus to
require 1.7 or was that a default? Can it be reset to 1.6 with no
loss of functionality?
DN policy is simple : there is inadequate resource to retain backwards
compatibility, so it is developed with current JDKs only. If anyone
wants to use an old JRE then use an old version of DN. Anyone objecting
to this can offer their time to maintain old versions (and as soon as
anyone suggests people doing stuff with their own time, all objections
strangely go quiet).
Current Status : DN 3.x will work with JRE 1.6. DN 3.x is no longer
developed, and doesn't have complete support for JDOQL "IF ELSE IF ELSE"
syntax.
I've never tried using DN 4.x with an old (1.6 or earlier) JRE. It
doesn't use that many JRE 1.7 methods IIRC but there may be some things
around JDBC used with JRE 1.6 having less methods, or maybe the ASM
bytecode enhancement has differences (there were definitely some in that
area). FWIW It is compiled with source/target as 1.7.
Why not try it?
Apache JDO may have to move to 1.7+ when/if API changes are proposed
that imply use of "new technology" (aka features in newer JDKs). Why
should people on old JRE's expect to get "upgrades" in features from
Apache JDO?
Do we have any customer feedback on the version level?
Some DN users are still using 1.6 but can continue using DN 3.x until
they upgrade their JRE. I don't see why they need an updated JDO API,
since their apps are typically mature, long running.
Will test the release early next week when back at base.
Regards
--
Andy Jefferson
DataNucleus (http://www.datanucleus.org)
