[JIRA] (JENKINS-15312) maven installation settings get lost

2012-10-03 Thread s.sog...@gmail.com (JIRA) 














































sogabe
 commented on  JENKINS-15312


maven installation settings get lost















the following changes will fix this.

https://github.com/jenkinsci/jenkins/commit/e6685a700c2c7e34f6cbd2c9ad474b2c201919f4#core/src/main/java/hudson/tasks/Maven.java



























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-15312) maven installation settings get lost

2012-10-01 Thread jeroen.ferdinan...@ovsoftware.com (JIRA) 














































Jeroen Ferdinandus
 commented on  JENKINS-15312


maven installation settings get lost















This is a duplicate of JENKINS-15293, workaround is using either 1.482 or configuring the Maven installations by hand (eg don't set it to install from Apache).



























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-15312) maven installation settings get lost

2012-09-30 Thread sak...@java.net (JIRA) 














































sakkew
 updated  JENKINS-15312


maven installation settings get lost
















Change By:


sakkew
(01/Oct/12 6:04 AM)




Environment:


Linux, Java 1.6
/Windows Server 2008 R2, Java 1.7



























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-15312) maven installation settings get lost

2012-09-29 Thread sak...@java.net (JIRA) 














































sakkew
 commented on  JENKINS-15312


maven installation settings get lost















I worked around this by overriding jenkins/tools-folder and jenkins/hudson.tasks.Maven.xml from another setup and then restarting Jenkins.
If you save Jenkins config even without doing any changes, the file hudson.tasks.Maven.xml gets reset, and maven is not found by builds anymore.



























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-15312) maven installation settings get lost

2012-09-26 Thread lfisc...@java.net (JIRA) 














































lfischer
 created  JENKINS-15312


maven installation settings get lost















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


maven



Created:


26/Sep/12 7:25 AM



Description:


After upgrading Jenkins to version 1.483, I see this behaviour:

Changing some (other) values on the Jenkins settings page, the Maven installation entries get lost after the save.
This results in broken maven build jobs, because they are missing their configured Maven installation.

Trying to reconfigure a Maven installation on the Jenkins settings page has no effect. After calling "save", the Maven entries disappear.

I have no log to present, because I had to downgrade Jenkins to version 1.481 to get my builds working.




Environment:


Linux, Java 1.6




Project:


Jenkins



Priority:


Critical



Reporter:


lfischer

























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