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
05:20:11 * For target buildtools_interim_langtools_modules_java.compiler.interim__the.BUILD_java.compiler.interim_batch:
05:20:11 warning: unknown enum constant Feature.SEALED_CLASSES
05:20:11 warning: unknown enum constant Feature.SEALED_CLASSES
05:20:11 error: warnings found and -Werror specified
05:20:11 1 error
05:20:11 2 warnings
SEALED_CLASSES is not defined in openj9 extensions jdk(next) yet as it has not been merged.
Whereas, Hotspot jdk15 builds already have this, hence as this is used as boot JDK for openj9 the compiler uses the constant in the interim code, hence the error...
Q: Should we use a OpenJ9 boot jdk for OpenJ9 builds...?
The text was updated successfully, but these errors were encountered:
karianna
added
bug
Issues that are problems in the code as reported by the community
openj9
Issues that are enhancements or bugs raised against the OpenJ9 group
labels
Jun 16, 2020
@andrew-m-leonard What timescale are we looking at until OpenJ9 implement the missing classes? Could we wait until they implement rather than adding in a specific use case?
Platform:
All OpenJ9 builds
SEALED_CLASSES is not defined in openj9 extensions jdk(next) yet as it has not been merged.
Whereas, Hotspot jdk15 builds already have this, hence as this is used as boot JDK for openj9 the compiler uses the constant in the interim code, hence the error...
Q: Should we use a OpenJ9 boot jdk for OpenJ9 builds...?
The text was updated successfully, but these errors were encountered: