At my company, at release time ( ie after we beat the heck out of snapshot build), we cut a release, but deploy to a staging repo. Then more ppl will test it. if approve, we use stage plugin to move the "entire" staging repo to a officially one.
if not approve, we yank the staging repo, do some fix and cut another release to staging. The process repeats until everyone likes it. Currently the stage plugin can only move source target thru http, to a target repo using scp. -D On Tue, Sep 23, 2008 at 1:47 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > (As I understand it...) > > Before the Maven dev team pushes builds out to the general public, > they get pushed to a staging repo where they can be fully tested. Once > the tests are complete, the files need to be pushed from the staging > repo to the "real" public repo. This plugin makes the process easier > and reduces errors. > > You can probably find more info about this plugin in the Maven Dev > list archives. > > Wayne > > On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad <[EMAIL PROTECTED]> wrote: >> Can anyone comment on the purpose [and status] of the 'stage' plugin? >> >> Apart from the statement >> >> Its main use is for copying artifacts from a staging repository >> to the real repository. >> >> at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't >> much explanation. I don't find many references to it in posts, nor >> does it seem to be addressed by the upcoming "Maven: A Definitive >> Guide" and older "Better Builds with Maven" texts. >> >> Specifically, what is a 'staging repository' [vs. a 'real repository']? >> >> Would the plugin be used to move all artifacts from one repo to >> another, or does it move only specific artifacts/versions? >> >> From content at >> http://maven.apache.org/plugins/maven-stage-plugin/usage.html, >> the answer would appear to be the former ... but I don't see much >> utility in that use case. >> >> What am I missing? Thanks. >> >> Brad >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
