2011/12/17 Mark Thomas <ma...@apache.org> > On 17/12/2011 18:08, Antonio Petrelli wrote: > > 2011/12/16 Mark Thomas <ma...@apache.org> > > > >> There are currently two options for publishing JARs to Maven Central: > >> 1. scp+rsync via people.a.o > >> 2. Nexus > >> > > > > In my experience in Tiles releases, the only problem we had with scp + > > simple copy (we did not use rsync) is that this process breaks Maven > > metadata. > > I try to explain myself. > > If you release to a staging directory, the Maven metadata (containg info > > about previous releases) are not there, so they are created from scratch. > > So, after releasing in the staging directory and voting, the copy method > > simply overwrite the old metadata with the new one (remember, *without > the > > old versions*). > > So in the end, we needed to use the Maven stage plugin (deprecated), > that: > > * downloads the staged artifacts; > > * reuploads them to the final destination. > > That is not an issue. > > Tomcat doesn't release to a staging repo first. The Maven artefact > release is only done after the release vote has passed. If you look at > the Tomcat 7 metadata you'll see that all versions are present. > > > Inside Nexus, you simply "promote" the staged repository, without the > > problem of downloading and uploading again. > > That is not a problem with the scp+rsync process used by the Tomcat > project. >
Ok then interprete my words as: now you can use a staging repository. This way, artifacts may be tested *before* they are released. Antonio
