-
Bug
-
Resolution: Unresolved
-
Critical
-
None
1. Create a new Freestyle project.
2. Add two "Invoke top-level Maven targets" build steps
3. Click "advanced" on each build specify and specify "-Dhttps.protocols=SSLv3 -Dforce.http.jre.executor=true" for JVM Options
4. Run the project. Notice that the JVM options are never used. Instead, I get this output:
[boost_snapshot] $ /home/builds/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_auto-install_/bin/mvn -Dsonatype_password=**** -Dsonatype_username=**** -Plinux-i386-gcc-debug deploy
This is reproducible always.
The reason I consider this critical is there is a critical Maven bug that we cannot work around without the ability to specify MAVEN_OPTS. See http://jira.codehaus.org/browse/MNG-5363 for more information.
Instead of specifying these values as "JVM Options", I specified them as "Properties" and it worked:
https.protocols=SSLv3 force.http.jre.executor=true
You can downgrade the priority of this bug but the issue remains: it's not clear why JVM Options are not passed on to "mvn". If you cannot pass on the options, they shouldn't be configurable in the first place.