|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)
- [JIRA] (JENKINS-15292) Redeplo... [email protected] (JIRA)

Ive got exactly the same issue (1.483), the only way around it is to add a pre-build step and execute a script to copy the global settings.xml to the local .m2/settings.xml......