Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65528

Option to avoid "Picked up JAVA_TOOL_OPTIONS" messages

XMLWordPrintable

      I started using the plugin, and in the FAQ it says that there is no way to avoid

      [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/path/to/workspace/...@tmp/withMaven.../pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/path/to/workspace/...@tmp"

      message.

      However, this results in red-colored messages all over the place.

      I have an idea on how to avoid this: introduce an option to put 

      -Dmaven.ext.class.path=".../pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="..."

      arguments into MAVEN_OPTS (optionally) instead of JAVA_TOOL_OPTIONS

       Something like

      withMaven(dontUseToolsOptions: true) { ... }

       

      This way, these messages can be avoided, and the release plugin functionality can be preserved.

      Currently, I am using something like this to avoid this issue, but it's cumbersome and not scalable:

      withMaven {
 sh """
 export MAVEN_OPTS="\$MAVEN_OPTS $JAVA_TOOL_OPTIONS"                    
 unset JAVA_TOOL_OPTIONS                    
 mvn verify \$(eval echo \$MAVEN_ADD_OPTIONS)
 """
}

          [JENKINS-65528] Option to avoid "Picked up JAVA_TOOL_OPTIONS" messages

          Arnaud Héritier added a comment -

          thanks for your feedback lprimak

          I'll try to look at it ASAP

          Arnaud Héritier added a comment - thanks for your feedback lprimak I'll try to look at it ASAP

          Lenny added a comment -

          Thanks Arnaud!

          Lenny added a comment - Thanks Arnaud!

          Lenny added a comment -

          Any updates on this issue? Thank you!

          Lenny added a comment - Any updates on this issue? Thank you!

          Cuba Stanley added a comment -

          Pinging this ticket again for updates - currently is causing some frustration in parsing pipeline output

          Cuba Stanley added a comment - Pinging this ticket again for updates - currently is causing some frustration in parsing pipeline output

          Lenny added a comment -

          The workaround does work:

          https://github.com/flowlogix/jenkins/blob/2c195907ce0de280cdc843a23712f5192bcc5ce0/UnitTests.groovy#L30

           

          sh """
export MAVEN_OPTS="\$MAVEN_OPTS $JAVA_TOOL_OPTIONS"                    
unset JAVA_TOOL_OPTIONS                   
mvn -B -C verify -fae -P$profiles \$(eval echo \$MAVEN_ADD_OPTIONS) ...

          Lenny added a comment - The workaround does work: https://github.com/flowlogix/jenkins/blob/2c195907ce0de280cdc843a23712f5192bcc5ce0/UnitTests.groovy#L30   sh """ export MAVEN_OPTS= "\$MAVEN_OPTS $JAVA_TOOL_OPTIONS" unset JAVA_TOOL_OPTIONS mvn -B -C verify -fae -P$profiles \$(eval echo \$MAVEN_ADD_OPTIONS) ...

            Unassigned Unassigned
            lprimak Lenny
            Votes:
            6 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: