You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tycho fails to find this jdk with useJDK = BREE configured, but no toolchain of type 'jdk' with id 'JavaSE-1.8' it would be good if tycho (when not finding a jdk by id) simply search one of type jdk+version=1.8 in this case
The text was updated successfully, but these errors were encountered:
Will work for pre 1.8 JVMs but IMHO it's time to stop care about them at all.
For 1.8 it will mismatch with compact profiles http://openjdk.java.net/jeps/161 .
For Java 9 and 10 - they are effectively dead now.
For Java 11+ aka modular Java BREE profiles no longer contain list of packages provided as this is runtime detected due to modularity.
With all that said - matching based on jdk+version for modular Java would make builds riskier and for old Java versions wouldn't benefit anyone as people either have figured this out already or won't bother supporting so old jvms for new stuff.
But especially for the auto detection there is a need to define toolchain (at laest tycho complains if none is found).
[WARNING] No system packages found in profile nor toolchain for JavaSE-16, using current JRE system packages.
This can cause faulty dependency resolution, consider adding a definition for a 'jdk' with id=JavaSE-16 in your toolchains.xml
So this would require a jdk with id = JavaSE-16 instead I think it would be valid to also considder an JDK with version = 16
Currently if there is a toolchain configured this way:
Tycho fails to find this jdk with
useJDK = BREE configured, but no toolchain of type 'jdk' with id 'JavaSE-1.8'
it would be good if tycho (when not finding a jdk by id) simply search one of type jdk+version=1.8 in this caseThe text was updated successfully, but these errors were encountered: