?
Thanks.
Matthew Jaskula
t +1 212.542.8299
From: Wayne Fay wayne...@gmail.com
Reply-To: Maven Users List users@maven.apache.org
Date: Wed, 3 Dec 2008 16:35:01 -0800
To: Maven Users List users@maven.apache.org
Subject: Re: How can maven be used in a continuous integration situation
On Thursday 04 December 2008 Wayne Fay wrote:
The problem with this method is that the maven install plugin only uses
the version in the pom file, not the version passed in on the command
line. This is noted in [this maven issue][1].
If you use mvn release rather than simply mvn install,
The latter, look at the link Wayne provided (maven-release-plugin).
Cheers.
2008/12/4 Martin Höller [EMAIL PROTECTED]
On Thursday 04 December 2008 Wayne Fay wrote:
The problem with this method is that the maven install plugin only uses
the version in the pom file, not the version passed
Jaskula
t +1 212.542.8299
From: Wayne Fay [EMAIL PROTECTED]
Reply-To: Maven Users List users@maven.apache.org
Date: Wed, 3 Dec 2008 16:35:01 -0800
To: Maven Users List users@maven.apache.org
Subject: Re: How can maven be used in a continuous integration situation?
The problem with this method
On Thu, Dec 4, 2008 at 10:29 AM, Matthew Jaskula [EMAIL PROTECTED] wrote:
Are you suggesting that our CI server performs a 'mvn release' nightly? From
the documentation that you linked to it seems like this is not intended to
be an automated process, as there are several steps that prompt the
that this is somehow not '*the maven way*'. So my question is, how
can maven be used in a continuous integration situation to install versioned
artifacts in the repository?
[1]: http://jira.codehaus.org/browse/MINSTALL-30
Thank you.
Matthew Jaskula
Engineer
Advanced Trading Solutions
NYSE
The problem with this method is that the maven install plugin only uses the
version in the pom file, not the version passed in on the command line. This
is noted in [this maven issue][1].
If you use mvn release rather than simply mvn install, this is
handled for you via the release plugin.