On 4/25/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > We need the shared artifacts to be available for build purposes but we > don't want to publish them to ibiblio. Its also a convenient staging > ground for ibiblio. Basically if you publish to the ASF maven repo it > starts complaining right away about signatures, etc. Plus we had > maven people promote stuff to ibiblio without us asking. > > What is the problem with an alternate repo? I think its a great idea. > People can test the "release" before its officially released.
Struts is planning to use maven-snapshot-repository for test builds (tagged and numbered, but not yet voted as a release.) To do this, we've overridden the definition of that repo to enable releases (because our test build will be versioned 1.3.2, with no -SNAPSHOT designation.) It's causing unnecessary traffic, but unless we establish another repo, I'm not sure what else to do. And then there is still an issue of how to promote artifacts from maven-snapshot-repository to dist/maven-repository. I want those *exact* artifacts moved to ibiblio. (In fact Maven's release process doesn't fit at all with the ASF way of voting on a particular set of files as "a release". The fact that the artifacts get rebuilt each time you deploy is a problem.) Brett suggested writing a plugin to do the "promotion", as Maven doesn't currently have a way to do it. -- Wendy
