> So it seems that the Platform no longer supports Java 5. Yes and no. As a whole, such for whole Eclipse SDK, even Kepler (If not Juno) said "Java 6 required", although there were always some bundles (and combination of bundles) that supported lower VMs. > Is this intentional and an unannounced policy change?
Probably not announced well. It has been discussed at status meetings, and various bugzillas, that some previous "1.4" or "1.5" bundles were moving to "1.5" or "1.6", but I am not sure there is yet a comprehensive list of those that have. (Other than looking in the manifests themselves). I think it's been assumed "no one cares about Java 1.5 any longer" ... so, if anyone does (i.e. you have requirements or customers with requirements for 1.5), then I suggest you open a bug on the specific use-case you need to support on 1.5 and what bundle changes prevent that. I'm sure the committers for those components would be willing to re-consider if it impacts adopters. But, the default assumption for testing should be "1.6" ... would be my personal advice. HTH From: Ed Willink <[email protected]> To: Cross project issues <[email protected]>, Date: 09/02/2013 11:02 AM Subject: [cross-project-issues-dev] Has Java 5 Platform support been discontinued? Sent by: [email protected] Hi Using a recent (post M1) platform I-build some of my unit tests now fail with a NoClassDef found for Platform. Changing the launch configuration to force JVM 6 and the tests run fine. So it seems that the Platform no longer supports Java 5. Is this intentional and an unannounced policy change? Regards Ed Willink _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
