[
https://issues.jenkins-ci.org/browse/JENKINS-12264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163219#comment-163219
]
Linus Tolke commented on JENKINS-12264:
---------------------------------------
I cannot reproduce your steps 1), 2) and 3). When I test this, neither editing
the Global MAVEN_OPTS in step 1) nor Executing a job in step 2) modifies the
jobs/<jobname>/config.xml file.
I assume that you, after step 1) and before step 3), have opened the configure
page for the job <jobname> and saved it again.
I have registered the bug JENKINS-13926 that addresses the problem with copying
the Global MAVEN_OPTS to the per-job MAVEN_OPTS when saving the job
configuration without the user being aware of it. The approach in JENKINS-13926
is that the mavenOpts tag should never have been written in the config.xml file
since it is only the Global MAVEN_OPTS that is set in your case.
> Cleaning "Global MAVEN_OPTS" fails to clean config.xml
> ------------------------------------------------------
>
> Key: JENKINS-12264
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12264
> Project: Jenkins
> Issue Type: Bug
> Components: maven
> Affects Versions: current
> Reporter: Luca Orlandi
>
> Steps to reproduce:
> 1) write -Dfoo=true in system configuration "Global MAVEN OPTS"
> 2) Execute a maven job (see the definition passing by in the console output
> 3) verify <MavenOpts>-Dfoo=true</MavenOpts> in jobs/<jobname>/config.xml
> 4) clean system configuration "Global MAVEN OPTS"
> 5) Re-execute the same maven job (definition is still there)
> 6) verify <MavenOpts>-Dfoo=true</MavenOpts> in jobs/<jobname>/config.xml
> for a correct behavior the mavenOpts tag in config.xml should be cleared.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
