I haven't tried this patch, but it looks like you're setting the information
once for all artifacts in the release process ? How would this work in a
multi-module release with different version numbers ?
I'm big +1 though on the idea of being able to run through release:prepare
without user intervention, either through POM configuration or system
variables.
Jorg
On 3/25/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
I have a very simple patch for the release-manager from trunk. It
let's you specify defaults for the release version and the new
version. Combined with -B you can completely automate your release.
These are the properties you need to set:
-Dmaven.release.version=<the release version>
-Dmaven.release.new=<the new development version>
>>>start of patch
Index:
maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/MapVersionsPhase.java
===================================================================
---
maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/MapVersionsPhase.java
(revision
519038)
+++
maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/MapVersionsPhase.java
(working
copy)
@@ -96,7 +96,7 @@
String nextVersion = null;
if ( version != null )
{
- nextVersion =
version.getNextVersion().getSnapshotVersionString();
+ nextVersion =
System.getProperty("maven.release.new",
version.getNextVersion().getSnapshotVersionString());
}
if ( releaseDescriptor.isInteractive() )
@@ -120,8 +120,9 @@
String nextVersion = null;
if ( version != null )
{
- nextVersion = version.getReleaseVersionString();
+ nextVersion =
System.getProperty("maven.release.version",
version.getReleaseVersionString());
}
+
if ( releaseDescriptor.isInteractive() )
{
<<< end of patch
On 3/25/07, Dan Tran <[EMAIL PROTECTED]> wrote:
> pass in -B, maven will use it own default values. Dont think you can
> overide the default value
>
> -D
>
>
> On 3/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > When running release:prepare, Maven stops and asks for user input to
> > define the release number for each module, the SCM tag to be used and
then
> > the new release number for each module.
> >
> > Is there a way to run release:prepare and pass all of that information
on
> > the command line or through a properties file so that I can get
> > release:prepare to run all the way through with no human interaction
being
> > necessary?
> >
> > Thanks.
> >
> >
> >
------------------------------------------------------------------------------
> > Craig Dickson
> > Software Engineering Manager
> > Behr Process Corporation
> > Santa Ana, California
> >
> >
> >
> > -------------------------------------------------------
> > The information contained in this e-mail message may be proprietary,
> > privileged, confidential or protected from disclosure. If you are not
the
> > intended recipient, any dissemination, distribution or copying is
strictly
> > prohibited. If you think that you have received this e-mail message in
> > error, please e-mail the sender.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
