• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • 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

          Andrew Bayer created issue -
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Attachment New: hudson.maven.MavenModuleSet.xml [ 18971 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: maven-plugin [ 16033 ]
          Component/s Original: maven2 [ 15487 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 135226 ] New: JNJira + In-Review [ 203342 ]

            abayer Andrew Bayer
            abayer Andrew Bayer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: