iginal Message-
> > From: dan tran [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 21, 2006 9:33 AM
> > To: Maven Developers List
> > Subject: Re: release:auto-release
> >
> > Mike, at my work, each daily build must accompany a label. So cut
> > t
---
> > From: dan tran [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 21, 2006 9:33 AM
> > To: Maven Developers List
> > Subject: Re: release:auto-release
> >
> > Mike, at my work, each daily build must accompany a label. So cut the
> > daily release is t
just use the scm:tag goal at the end of your build?
>
> -Original Message-
> From: dan tran [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 21, 2006 9:33 AM
> To: Maven Developers List
> Subject: Re: release:auto-release
>
> Mike, at my work, each daily build must accom
21, 2006 9:33 AM
To: Maven Developers List
Subject: Re: release:auto-release
Mike, at my work, each daily build must accompany a label. So cut the
daily release is the way to go. I also work with another smaller
project that adopting maven release process where daily build is from
the snapshot
Mike, at my work, each daily build must accompany a label. So cut the
daily release
is the way to go. I also work with another smaller project that adopting
maven release
process where daily build is from the snapshot build, we only cut a release
when a
millestone reaches.
-D
On 4/21/06, Mi
Why would you ever want to auto-release something? Isn't a release done
when the module owner believes it is stable, not on an scheduled time
table? I would think a daily release should take the form of a
SNAPSHOT.
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Thursd
Hi Brett,
Since You are on it, please work on it, I will test it instead.
Thanks, and glad to retire my custom plugin.
-Dan
On 4/20/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Sounds good.
>
> I'm actually (finally!) working on the plugin, so I can work this in if
> you'd like. If you alre
Sounds good.
I'm actually (finally!) working on the plugin, so I can work this in if
you'd like. If you already have time to work on it now, let me know. I
imagine this will be pretty straightforward.
I'd call it release:release, and would expect it to behave just like
release:prepare release:per
