----- Original Message ----- > From: "Christopher" <ctubbsii-fedora@xxxxxxxxxx> > To: "Deepak Bhole" <dbhole@xxxxxxxxxx> > Cc: "Fedora Java Development List" <java-devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Friday, October 31, 2014 8:55:39 PM > Subject: Re: Eclipse Luna on Fedora 21 and JDK 8 requirement > > On Fri, Oct 31, 2014 at 2:30 PM, Deepak Bhole < dbhole@xxxxxxxxxx > wrote: > > > * Christopher < ctubbsii-fedora@xxxxxxxxxx > [2014-10-31 14:02]: > [snip] > > > > > There is no issue with -target 1.6; the issue was with strict source > > compatibility with 1.6. I can't recall the specifics (it had something to > > do > > with generic type checking, because 1.7's javac can make better > > inferences), > > but that's outside the scope of this issue. The main point, as it relates > > here, > > is that there may not be strict compatibility between javac provided by > > different JDKs, even if javac makes a best effort attempt to parse older > > source. A more obvious problem is the lack of bootstrap classpaths for > > older > > -source/-target, which is known to be likely to create compiled code that > > is > > not capable of running in an older JVM (this doesn't matter if you're > > developing for the latest Fedora, but it matters if you're using the latest > > Fedora to develop for other platforms, like RHEL or Android). > > > > Ah, yeah not much we can do (with current setup) where the older rt.jar > is needed on bootstrap path :/ > > [snip] > > Well, what we could do is rethink the policy about not packaging currently > supported JDKs, just because they are expected to not have further updates > at some future time. That policy's going to bite us anyway, if the pace of > Java ever reaches a point where a version of Java is released *and* EOL'd > during the same window (hypothetically, Java 8 is expected to EOL during > F22, and Java 9 is expected to be released and EOL'd during F22; would that > mean F22 cannot include any Java version?). > > Personally, I like the idea of shipping the latest as default, and the next > most recent (so long as it is currently supported) as available as an > SDK/devel package and just stop updating it when there aren't any more > upstream updates and drop it from the next release. So do you also sign for doing the work needed incl. the security fixes and etc.? There is no policy that we should ship only single JDK as far as I know, it's a result of the resources available from my POV. To keep it on Eclipse side even if two JDKs are available in fedora I would test and target only the latest one with Eclipse unless someone joins to share the burden of verifying it works on the other one. Alexander Kurtakov Red Hat Eclipse team > > -- > Christopher L Tubbs II > http://gravatar.com/ctubbsii > > > -- > java-devel mailing list > java-devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/java-devel -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
