Hi Marty, Having a CI snapshots build repository is not solely for the purpose of distinguishing between CI deploys and user deploys.
You can configure your dependency resolution tool to resolve artifacts from a specific repository, you may want for one project an artifact hosted on libs-releases-local, and another project that uses the same artifact but is hosted on another repository on ext-releases-local. The naming is used mostly for categorization and classification of artifacts. This separation of repositories allows for higher flexibility of resolution and deployment as to where to get the certain artifact which you wish to resolve, or to where to deploy. Thanks, Tomer On 07/21/2010 04:49 PM, MartyMcFly wrote: > Thanks Tomer. > > I was confused by the repositiers libs-snapshots and libs-snapshots-local > and respectively libs-release. So actually I meant why not using these > "local" repostories. > > Your link about the promotion is not helpful for me as this shows features > not available in the open source edition. > > So the reason for having a differnt repository for CI snapshot builds is > soley for distinguish between e.g. CI deploys and user deploys ? or other > said - what or who deploys then to libs-snapshots-local or > libs-release-local ? > > Thanks again > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
