-
Bug
-
Resolution: Fixed
-
Major
-
None
The global MAVEN_OPTS option isn't actually saving anything - turns out the underlying problem here is that I needed to add TopLevelItemDescriptor to the list of descriptors that get configure called against them when the global configuration is saved, and I needed to tweak the global.jelly for MavenModuleSet to use ${descriptor.globalMavenOpts}, not ${it.globalMavenOpts}.
[JENKINS-5142] Global MAVEN_OPTS setting not registering
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Attachment | New: hudson.maven.MavenModuleSet.xml [ 18971 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: maven2 [ 15487 ] |
Workflow | Original: JNJira [ 135226 ] | New: JNJira + In-Review [ 203342 ] |
Code changed in hudson
User: : abayer
Path:
trunk/hudson/main/core/src/main/java/hudson/model/Hudson.java
trunk/hudson/main/maven-plugin/src/main/resources/hudson/maven/MavenModuleSet/global.jelly
trunk/www/changelog.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=24844
Log:
[FIXED JENKINS-5142] TopLevelItemDescriptors now have configure called against them