|
||||||||
|
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-15292) RedeployPubl... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... scott.brinkme...@nwea.org (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... jeffmaury.jenk...@jeffmaury.com (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... ol...@apache.org (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... scott.brinkme...@nwea.org (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... i...@sven-amann.de (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... dogf...@java.net (JIRA)
From the respective changeset I take that maven default settings are considered automatically if MVN_HOME is set, right?
The error occurs in case the user-wise maven config doesn't exist, because the code tries to copy the file anyways what results in FNF. Therefore, if the code doesn't need to fall back to the maven default config, because that happens automatically, you should just avoid the copy in case the target file is missing? I'm not sure about how the config files behave though...