> 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.
One advantage in establish a myfaces repo is that we can designate it as "release" only in the <repository> config. This way its only checked if the artifact cannot be found in ibiblio and only if its *final.* No snapshots are ever checked. Is this right? And if so, does this make sense 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. There is the signing of the artifacts as well as the actual publishing. Maybe we could work together on a solution for that. > Wendy Sean
