[
https://jira.codehaus.org/browse/MNG-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders Hammar updated MNG-5362:
-------------------------------
Priority: Major (was: Critical)
Lowering priority.
I don't follow, could you please explain what solutions you've tried that are
frustrating.
Also, you say you cannot use "nonunique" snapshots as they name needs to be the
same over builds. Don't you mean that cannot use UNIQUE (timestamped) snapshots?
> Option to always download SNAPSHOT from remote repo
> ---------------------------------------------------
>
> Key: MNG-5362
> URL: https://jira.codehaus.org/browse/MNG-5362
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Venkata
>
> It should be possible for a project to always download a remote SNAPSHOT
> artifact when mentioned as part of the dependency.
> Consider our scenario, where we have two projects - projA and projB, projA
> depends on projB - under active development.
> CI Builds happen on a cluster of 4 servers. ProjB ends up throwing errors
> very frequently because latest of ProjA would have been compiled on a
> different server than ProjB.
> For organizational reasons, we cannot make our Artifactory repo to use
> 'Nonunique snapshots', i.e. we need the artifact name to be same for each
> update in Maven repo.
> I am pretty sure that many people out there have been facing the same issue.
> There are other solutions, but all of them are equally frustrating.
> It would be nice to have an updatePolicy of 'force' or something which will
> always reach out to latest snapshot version.
> Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
