On Fri, Dec 16, 2011 at 12:44 AM, Jörg Schaible
joerg.schai...@scalaris.com 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.
On Fri, Dec 16, 2011 at 4:51 AM, Olivier Lamy ol...@apache.org 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
On Fri, Dec 16, 2011 at 6:24 AM, Thiessen, Todd (Todd)
tthies...@avaya.com 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
2011/12/15 Phillip Hellewell ssh...@gmail.com:
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
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 prepare
phase won't actually try and build the snapshot.
IMHO, your second
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
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.
-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
Sent:
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
On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
tthies...@avaya.com 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
On Thu, Dec 15, 2011 at 3:07 PM, pino.silvag...@gmail.com 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.
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 control on
Hi Phillip,
Phillip Hellewell wrote:
On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
tthies...@avaya.com 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
12 matches
Mail list logo
