|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
After further investigation, it looks like this is only an issue when a snapshot version exists in multiple snapshot repositories (in my case, nexus and jenkins-upstream).
I've changed our repository configuration to work around this. Luckily we can do this, although depending on your nexus repo configuration it may not be easy to do for all users.
If this is not a supported configuration it really should be explicit in the documentation. However if the plugin was wrote the correct metadata then I would assume maven would simply retrieve the most recent version of the snapshot from the repository where it exists.