Brian Mericle created JENKINS-14054:
---------------------------------------
Summary: The "Root POM" field value in the Build section of a
Maven job configuration is not being read in.
Key: JENKINS-14054
URL: https://issues.jenkins-ci.org/browse/JENKINS-14054
Project: Jenkins
Issue Type: Bug
Components: maven2
Affects Versions: current
Environment: Linux version 2.6.18-308.4.1.el5
(mockbu...@hs20-bc2-4.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat
4.1.2-52)) #1 SMP Wed Mar 28 01:54:56 EDT 2012
Red Hat Enterprise Linux Server release 5.8 (Tikanga)
Reporter: Brian Mericle
Fix For: current
I'm currently using version 1.467. The value in the "Root POM" field in the
"Build" section of a Maven job configuration is not being read in when the
configuration is loaded. If you modify the job configuration, the "Root POM"
field is blank. If you fill in the "Root POM" field and save, the job will work
correctly, but if you neglect to fill it in, even if you modify something else
within the job, it will break the build. This is causing some of our jobs to
fail b/c the pom.xml file that needs to be executed is not in the root folder
of the Workspace. I believe this was introduced in version 1.466 with the
following snippet from the release notes "Maven plugin: expand variables in
"Room POM" field (issue 13822)".
--
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
