Mark Donszelmann a écrit :
Hi
On Jun 6, 2007, at 4:41 AM, Graham Leggett wrote:
On Tue, June 5, 2007 9:06 pm, Brett Porter wrote:
Right. The reason for not choosing to install by default is that you
end up with a "release" in your local repository which is not the
final one.
We've run into this problem as well - the version being tested, as far as
I am aware, is the SNAPSHOT version, meaning that at the end of this, an
up to date build of snapshot will be included in the local repository,
which is perfectly reasonable.
The workaround for us to release aggregated projects is like this:
mvn install release:prepare
but this would do the install w/o the poms being changed from
3.3-SNAPSHOT to 3.3,
so this would not help.
If you want to install artifacts in your local repo during the prepare process and don't want to use 'clean verify' goals, you can configure preparationGoals parameter on the prepare mojo
(http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html)
Emmanuel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
