Can't we have something similar to the site:deploy/site:publish goals in m1
?
By default the team deploy the artifact on a staging repository and when the
release is graded the team publish it on the main repository.
I think that it is easy to do in m1.
I don't know for m2.

Arnaud

On 4/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Unfortunately the support for this is not going to be great. We don't
> have any type of repository promotion (yet) for something already
> released.
>
> I'd suggest using profiles, but distributionManagement can't currently
> be in a profile.
>
> I think you should have your test repository somewhere as the default
> in the distributionManagement and deploy there, and when you decide to
> promote it, check out the tag, modify the pom, and deploy it again.
> This will rebuild the artifacts however - so I'm not sure if that's
> satisfactory.
>
> Maybe a custom deployment plugin is in order here?
>
> - Brett
>
> On 4/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > In another thread about Maven 1 [1] the idea of httpd- and
> > Tomcat-style releases came up, where a build is produced and numbered
> > x.x.x, and then it is later graded.  Struts has also adopted this
> > style of test-build/release.  And we're in the process of converting
> > the Struts Action 1 build to Maven 2. :)
> >
> > How does Maven 2 handle this style of releasing?
> >
> > Ideally, we would "release" the test build to a snapshot repository
> > for evaluation.  Given the amount of metadata that goes along with
> > Maven build artifacts, what's the best way to 're-deploy' everything
> > to a distribution repository once it is graded and approved as an
> > actual release?
> >
> > [1] http://www.nabble.com/Re%3A-Maven-1.1-gold--p3813013.html
> >
> > Thanks,
> > --
> > Wendy
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

Reply via email to