|
||||||||
|
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-15976) Provided maven setti... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)
- [JIRA] (JENKINS-15976) Provided maven ... [email protected] (JIRA)

I've just confirmed with Stephen C. on IRC that this happens in the freestyle projects: the configuration setting cannot be set, it'll be lost like the original poster said.
Would be great to see this fixed. While we can use the -s trick, having the setting there causes confusion.