Hi, my main concern is that I don't like to maintain two JRE on my (windows) PC. I see warning messages when I compile with JDK 1.7 and target 1.6: [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6 I did not find out how to fix this and I don't know what it means if I post a jar file and one tries to run it on 1.6. Gerd Steve Ratcliffe wrote
Hi
On 24/09/13 18:50, WanMil wrote:
I don't like rolling back to Java 6 but I would not veto. @Steve, Gerd: what's your opinion about rolling back to Java 6?
I'm not in any rush to use any Java7 only features, so it is up to you guys whether you actually do. But I think we should look at it this way:
If we had a different release policy where we had a stable release, say version 2.6.3, and a development branch working towards version 3.0.0 then that development branch might be delivered in 6 months or even a years time. People kind of expect that with software.
In such a case I think it is would be reasonable to target the development branch at Java 7, since the expected release date would then be over a year after the Oracle Java 6 end-of-life date (although I know that they have put out a few bug fix releases after February).
But instead we have a continuous release policy, and so a switch to Java 7 hits everyone at the same time. But we could easily also support a Java 6 release.
So what I propose to do is to fully switch trunk builds to Java 7 and create a separate 'stable' release for Java 6 which would be at the latest version that would still build with 6. At intervals, depending required effort and demand, this version could be updated by porting over the changes, using openjdk sources if necessary.
..Steve _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2714-Make-java-1-7-mandatory-and-refu... Sent from the Mkgmap Development mailing list archive at Nabble.com.