[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
Title: Message Title Michael Paesold commented on JENKINS-14054 Re: The "Root POM" field value in the Build section of a Maven job configuration is not being read in. No, I can't reproduce either. Earliest tested version is LTS 1.609.3. That and all later versions are good. I propose to resolve this issue. Any objections? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
Michael Paesold commented on JENKINS-14054 The "Root POM" field value in the Build section of a Maven job configuration is not being read in. Same here - a rather painful regression. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
edbras commented on JENKINS-14054 The "Root POM" field value in the Build section of a Maven job configuration is not being read in. Same experience here... Simple open the project, fill the root pom field, press save and open the config page again -> root pom field empty. However it's used, so it's only a display issue I quess, and it uses the empty value when pressing the save button again. So you must always fill it in as a workaround if you want to presse the save/appy button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
Harry Braun commented on JENKINS-14054 The "Root POM" field value in the Build section of a Maven job configuration is not being read in. We can't use the sonar-plugin and everytime we open the configuration the root pom is empty. So we think about going back to 1.465.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
[ https://issues.jenkins-ci.org/browse/JENKINS-14054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163660#comment-163660 ] Pete Hammond commented on JENKINS-14054: I upgraded to 1.467 from 1.465 yesterday (06-06-2012) and the same thing is happening on all of my jobs. The root pom field is not being retained, I fill it in run a build, it works. the next time a developer checks in the job runs and fails with pom not found. > 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 > Labels: build, maven2, pom, root > 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
[JIRA] (JENKINS-14054) The "Root POM" field value in the Build section of a Maven job configuration is not being read in.
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
