|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
I'm also running into this issue and would be very leery of running mvn install before deploying jobs simply because we're running about 100 projects across 500 jobs or so and need to make sure that the versions that we're building with match what the entire engineering team is using. If mvn install worked but the upload failed for some reason, we could end up out of sync and have in the past when we were doing installs.
Does anyone know any other work arounds? I don't seem to be running into the issue using maven 3.0.1 but any build I move to 3.0.4 has this issue and I desperately need to move up to correct an issue in 3.0.1.