On 2/26/08, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > It has been used internally by the Maven developers for quite some time > now. The main purpose is to move artifacts from a staging repository to > the real repository. > > A staging repo, usually put in a user's home directory on people, is > used for staging a release. From there is will be checked by the pmc and > other interested parties. >
I like this idea. I tinkered with the idea of having m2 "deploy" my artifacts to a dummy repository inside my home directory on people.apache.org, by overriding the deployment settings in the "rc" profile. But, I ended up doing it manually because I wanted everything to live in a directory name suffixed by the release candidate number (rc4 for example). Subsequent deployments would actually overwrite the previous release candidate's artifacts and I wasn't too sure that was the right thing to do. > If the release is deemed fit for public consumption, the stage-plugin is > used to copy the artifacts from the staging repo to the apache > repository-sync-directory. > > It helps people who want to use Maven 2 as the build tools and at the > same time being able to vote on the actual bits of a release. > > -- > > Dennis Lundberg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
