[
https://jira.codehaus.org/browse/MNG-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312297#comment-312297
]
Venkata commented on MNG-5362:
------------------------------
Hi Anders,
Thanks for response.
I meant 'unique' where I said 'nonunique'. If possible, please edit it (I do
not seem to have privileges).
Following are the solution I have tried:
1. -U flag. It is still at the mercy of Maven ascertaining that there is a new
update available.
2. I have considered using cron, but we have a combination of windows and Linux
build boxes. Also, developers are using Windows boxes. We can put in a
'process' for a mechanical activity.
3. Currently, I have all the build happening on a single server, which kind of
becomes a bottleneck
4. Developers frequently give me the 'Works on my workstation' and they cannot
be questioned because they may be right (mitigated to a large extent by #3, but
still frustrating).
5. Currently, I am trying to put in 'purge-local-repo' into each build we have,
but still will be painful because we have to enable each maven build and each
build will go crazy downloading files after that. Also, it will cause issues
when two builds are triggered with common dependencies. They WILL delete files
needed by each other, producing inconsistent build breakages.
These are probably the biggest pain points.
> 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
