"scott.stark(a)jboss.org" wrote : | "pgier" wrote : | | How should we handle thirdparty jars in our repository? One way is to set up a separate repository just for thirdparty artifacts. Another way is to allow developers to add thirdparty stuff to the snapshot repository, and then copy the required files to the release repository when a release is performed. | | | I still need the behavior of snapshot vs non-snapshot described better. We already have 'snapshot' releases in jboss and maven repositories. How does a snapshot repository come into the picture and help things. Layout the pros and cons. | The goal of the snapshot repository is to separate development builds from release builds. Eventually we would like to have only a limited number of people with access to the releases (including alpha, beta, etc) repository. The snapshot repository will be available to all developers and will change much more often. The limitations with the current single repository system are: 1. Release versions of artifacts can be changed by any developer with commit access to the repository. 2. There is not an easy way to clean up old builds. 3. Deploying to the repository requires the extra step of committing, and a time delay before the files appear in the repo. 4. We don't have a way to prevent snapshot versions of dependencies from being included in a release. Having a separate snapshot repository will resolve these issues. We also don't need to have snapshots under version control. I think that maven repositories are not really meant to be under version control. The snapshot builds are basically temporary files, and the release repository should be add only and part of the release process. But it doesn't really hurt to have the releases in cvs or svn. The only drawback I can think of is the extra complexity of having the two separate structures. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024759#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...