Hi Marty,It is best practice to define a new repository for builds that are deployed to a repository manager so you can distinguish those artifacts from others. It is also useful when wanting to promote artifacts from a repository that are ready to be released to another repository (see: http://www.jfrog.org/confluence/x/JACq) the fact that the new repository was defined to accept both releases and snapshots was to demonstrate the features that a repository has, it is however not recommended to define it as such.
The reason you cannot deploy to "libs-snapshots" or "libs-releases" is due to the fact that those are virtual repositories (see: http://www.jfrog.org/confluence/x/GgCq) and are used to aggregate cached/local repositories. You can only deploy to local repositories.
Thanks, Tomer Cohen On 07/21/2010 01:55 PM, MartyMcFly wrote:
Hi all, I jsust started to use artifactory and watched the screencasts about hudson and artifactory. I was wondering - why is a new repository for hudson defined (which accepts releases& snapshots). Is there a reason why the libs-snapshots or libs-releases repository is not used ? Thanks for the clarification
------------------------------------------------------------------------------ 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
