Like I said, it's a very simple patch. I use it because I want to
release a big multi-module project with the same (non-default) version
for all modules.
tom
On 3/26/07, Jorg Heymans <[EMAIL PROTECTED]> wrote:
I haven't tried this patch, but it looks like you're setting the information
once for
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 inter
related JIRA
http://jira.codehaus.org/browse/MRELEASE-100
please vote
-D
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 c
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=
-Dmaven.release.new=
start of p
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 us
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 pr
