On Fri, Dec 16, 2011 at 6:24 AM, Thiessen, Todd (Todd)
wrote:
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
>
> If you look at the preperationGoal option of the prepare goal, you will see
> the default is clean verify. If you change with to simple be clean, the
> prep
On Fri, Dec 16, 2011 at 4:51 AM, Olivier Lamy wrote:
>
> As you use svn, a possible solution is to use remoteTagging=false
> (http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging)
>
> which do svn cp . http://blbl/tags/
Thanks for the tip, but I don't think that ha
On Fri, Dec 16, 2011 at 12:44 AM, Jörg Schaible
wrote:
> Phillip Hellewell wrote:
>> Thanks Todd; can you give me a hint on how to change the goals that
>> get run by release:prepare?
>
> See configuration parameters of realase:prepare.
Ah yes, here it is: "preparationGoals". Thanks. I don't kn
On Thu, Dec 15, 2011 at 7:16 PM, Benson Margulies wrote:
>> Do you mean "branch" or "tag"?
>
> A branch.
>
> In a busy environment, the common practice is:
>
> 1) use release:branch to make a branch.
> 2) use release:prepare/perform on the branch
Ok, I get it now. So then do you also delete the
ld to be broken.
> -Original Message-
> From: Phillip Hellewell [mailto:ssh...@gmail.com]
> Sent: Thursday, December 15, 2011 6:48 PM
> To: Maven Users List
> Subject: Re: Release plugin should tag the revision that was built in
> the prepare phase
>
> On Thu, Dec 15
2011/12/15 Phillip Hellewell :
> So release:prepare does a compile first and then (modifies the pom and)
> creates the tag. That makes sense, but...
>
> the problem is we have some artifacts that take a *long* time (up to an
> hour) to build. During that time developers may check in more changes
Hi Phillip,
Phillip Hellewell wrote:
> On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
> wrote:
>> You can skip the building of the snapshot by changing the goals in the
>> prepare phase. This will then jump you right to tag creation, checkout
>> of the tag and building of the tag during
> Do you mean "branch" or "tag"?
A branch.
In a busy environment, the common practice is:
1) use release:branch to make a branch.
2) use release:prepare/perform on the branch
>
> A release is created from a tag, and that is what the release plugin
> does for us.
>
>> Unless you have total co
On Thu, Dec 15, 2011 at 3:07 PM, wrote:
> Maybe I didn't fully get every steps of your release
> but usually you should branch your code and release
> from there.
Do you mean "branch" or "tag"?
A release is created from a tag, and that is what the release plugin
does for us.
> Unless you have
On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
wrote:
> You can skip the building of the snapshot by changing the goals in the
> prepare phase. This will then jump you right to tag creation, checkout of
> the tag and building of the tag during the perform phase.
Thanks Todd; can you gi
Maybe I didn't fully get every steps of your release
but usually you should branch your code and release
from there.
Unless you have total control on your branch/trunk, even then
the best approach should be to branch. We branch on first beta
or code/feature freeze.
On , Phillip Hellewell wrote:
> Sent: Thursday, December 15, 2011 4:58 PM
> To: Maven Users List
> Subject: Release plugin should tag the revision that was built in the
> prepare phase
>
> So release:prepare does a compile first and then (modifies the pom and)
> creates the tag. That makes sense, but...
>
So release:prepare does a compile first and then (modifies the pom and)
creates the tag. That makes sense, but...
the problem is we have some artifacts that take a *long* time (up to an
hour) to build. During that time developers may check in more changes that
they don't expect to be part of the
13 matches
Mail list logo
