`
yangyi
  • 浏览: 112821 次
  • 性别: Icon_minigender_1
  • 来自: 北京
社区版块
存档分类
最新评论

Be careful about the snapshots

阅读更多
We are a global team with around 30 devs that generally focusing on the same product. And we have a mirror site of maven repo maintained using Nexus. The proxy server is placed in the US and when we start checking out the latest code and rebuild, it usually takes the Beijing team a lot of time.
The problem here is we use some snapshot libs on glassfish related libs, every 24 hours, these libs will be downloaded again, and nothing would be expected to change.
The idea of snapshot for maven is that when someone actively developing some code, which is referenced by your project in the pom, you then can be guaranteed to have the lasted dependency without changing pom. So for those libs that are out of the ctrl scope, the better use case is to retrieve them from the release-repo.
That's the raw idea. Or perhaps maven can skip checking update for some snapshots locally? I haven't examined this.
0
0
分享到:
评论
3 楼 yangyi 2011-06-18  
liangcoder 写道
maybe, you can have a try with "-o" parameter when executing the "mvn" commands, which refers to the offline model

Thanks, that would be greatly helpful
2 楼 liangcoder 2011-06-18  
maybe, you can have a try with "-o" parameter when executing the "mvn" commands, which refers to the offline model
1 楼 liangcoder 2011-06-18  
The snapshot version is based on the timestamp. u know, all of your team members need to download some lib every 24 hours, that means there must be some changes on them due to the re-deployement.

相关推荐

Global site tag (gtag.js) - Google Analytics