-
Notifications
You must be signed in to change notification settings - Fork 874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move java modules job to JDK 11 and fix tests where needed #5138
Conversation
809a07e
to
4cdfe38
Compare
test.jms.flags=--limit-modules=java.base,java.logging,java.xml,java.prefs,java.desktop,java.management,java.instrument,jdk.zipfs,java.scripting,java.naming | ||
test.bootclasspath.prepend.args=-Dno.netbeans.bootclasspath.prepend.needed=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this has almost the same effect as the old CI config line:
OPTS_11=-Dtest.run.args=--limit-modules=java.base,java.logging,java.xml,java.prefs,java.desktop,java.management,java.instrument,jdk.zipfs,java.scripting,java.naming -Dtest.bootclasspath.prepend.args=-Dno.netbeans.bootclasspath.prepend.needed=true
the difference is that the entire run args property isn't overwritten which is set up here:
netbeans/nbbuild/templates/projectized.xml
Line 293 in 30a8cef
<property name="test.run.args" value="-ea -Xms1200m -Xmx1200m -XX:+UseParallelGC ${metabuild.jms-flags.jvm} ${test.jms.flags} -XX:+IgnoreUnrecognizedVMOptions"/> |
this has however the side effect of warnings like:
WARNING: Unknown module: jdk.compiler specified to --add-exports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, i got an idea while waiting for Santa.
we can simply unset the default flags of the compiler category:
# remove default compiler JMS flags so that we don't get "Unknown module" warnings due to --limit-modules
jms-compiler.flags.jvm=
since we split them into categories already (#3658) we may as well make use of that fact :)
- put java module system flags into project properties instead of CI config. - allows running the tests out-of-the-box from IDE - has the benefit of not overriding other JVM flag defaults for CI - move whole job from 8 to 11 and remove (now) redundant steps - ModuleTest: fix JRTFS module root for JDK 9-12. - remove empty ConstantPoolTest
4cdfe38
to
26e47e1
Compare
@jlahoda would be good if you could take a look at this one. |
@neilcsmith-net I have this one set for NB17 since this reduces the longest job by about 30mins, since releasing does require a lot of building I thought it would be good to get this one in. |
thanks for the review. Lets get this in. |
move java modules job to JDK 11 and fix tests where needed.
meta issue #4904