It should cover the topic of Native Multi Release Compilation support in JDT:
JDT now supports compilation of "Multi-Release-Types", that is the same class exits in different variants with the same name and can simultaneously be edited and compiled and automatically be placed in appropriate output folders.
It maps to an approach described as "Pattern 3: Single Project" described here https://maven.apache.org/plugins/maven-compiler-plugin/multirelease.html and as described in the "Challenges" section currently there is no good IDE support for that case, we solve this now by using the "highest" JDK and compile individual class files with the according release option.
The other patterns work, but they require a much more sophisticated setup in the IDEs and are usually not directly executable or requires a lot of custom configuration:
Now it becomes incredible simple when used with Eclipse IDE/JDT by just setting a simple option the classpath dialog of a source folder!
To promote this new feature we should write a good summary as a N&N entry;
It should cover the topic of Native Multi Release Compilation support in JDT:
JDT now supports compilation of "Multi-Release-Types", that is the same class exits in different variants with the same name and can simultaneously be edited and compiled and automatically be placed in appropriate output folders.
It maps to an approach described as "Pattern 3: Single Project" described here https://maven.apache.org/plugins/maven-compiler-plugin/multirelease.html and as described in the "Challenges" section currently there is no good IDE support for that case, we solve this now by using the "highest" JDK and compile individual class files with the according release option.
The other patterns work, but they require a much more sophisticated setup in the IDEs and are usually not directly executable or requires a lot of custom configuration:
Now it becomes incredible simple when used with Eclipse IDE/JDT by just setting a simple option the classpath dialog of a source folder!
To promote this new feature we should write a good summary as a N&N entry;