Community
Participate
Working Groups
Due to bug 463433, it became harder to set up a build that checks strict JavaSE-1.6 compatibility. Since Java 6 can no longer be used to run Tycho, you'd need to set up special runtime libraries for the compilation ("BREE libs") and/or toolchains for the test execution to do this. Therefore it probably makes sense to change the default execution environment and compiler source/target levels in Tycho to 1.7.
those who care about strict API compatibility set up BREE libs for all EEs anyway and always declare a BREE. You can't really expect to have strict API compatibility checks without using toolchains (unless you happen to use the same BREE for all your bundles and this happens to be at least the minimum required to run Tycho builds). But thinking about it, I have a different argument for changing the default EE: If you build using Java 7, you expect Java 7 packages to be resolvable by p2.
+1 from me for doing this change for 0.23.0.
Changes for Tycho Core: https://git.eclipse.org/r/#/c/45443/ Changes for Tycho Extras: https://git.eclipse.org/r/#/c/45636/
Changes submitted with commit: Tycho Extras: http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/commit/?id=69a7ae223eccb65ff8ae4baf7cc3406b1eaa388f Tycho Core: http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=d44d8e976b233703dedfdcbef4d05ed6c55428d5