Community
Participate
Working Groups
We have a number of bugs where parts (not all) of the problems would not have been possible when the code for java 1.6 compatibility would have its own project with clear java 1.6 compliance settings. Currently within one project parts of the code need to be java 1.8 and part of it java 1.6 compatible while the project settings are java 1.8. https://git.eclipse.org/c/platform/eclipse.platform.git/tree/ant/org.eclipse.ant.launching/.settings/org.eclipse.jdt.core.prefs?id=faa77f958bca6aa3ca2c281d508acf0710be9032 see https://bugs.eclipse.org/bugs/show_bug.cgi?id=558324 https://bugs.eclipse.org/bugs/show_bug.cgi?id=495617 https://bugs.eclipse.org/bugs/show_bug.cgi?id=553514 https://bugs.eclipse.org/bugs/show_bug.cgi?id=558330 In the long run I wonder if it would be possible to provide a solution with separate jars for different BREEs and a automatic switch so that we can use latest features and still update the code for use with latest java versions. Or there is a completely different long term solution? At least to have a java 1.6 dependency and code that needs to conform to java 1.6 as part of eclipse looks highly suspicious. What if someday this code cannot be run with latest java versions at all? Here a link to the story that you find as well in one of the bugs: http://blog.sibvisions.com/2015/09/25/eclipse-mars-with-ant-and-jre-6-story/
