>+1
>I wouldn't try folding it into 3.x until the project builder
>refactoring is done.
We were talking about the new 2.1, not 3.0 right away.
--Brian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
we could add the parallel download and release as 2.2 etc.
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2008 8:38 PM
To: Maven Users List; Maven Developers List
Subject: New sandbox plugin: maven-reactor-plugin
I've checked in a new
Jamie Whitehouse wrote:
Would it make more sense for the make.folders parameter to be named
make.modules to keep it consistent with the same concept in multi-module
builds?
I called it "folders" because you have the choice of specifying folder
names or artifact names with make.artifacts.
Ch
Nick Stolwijk wrote:
Shouldn't those examples include one or multiple goals and/or phases? Or
will it always execute install?
Yes, check out the examples here:
http://maven.apache.org/plugins/maven-reactor-plugin/examples.html
One example:
mvn reactor:make -Dmake.folders=barBusinessLogic -Dm
Tobias Gierke wrote:
First of all, thanks for your work on this plugin...it really eases the pain
;) As far as i know, no other plugin uses camel-case goal names. Wouldn't it
be more consistent to name them "make-my-changes" and "make-scm-changes" ?
Yup, I've already changed it:
http://maven
gt;>>
>>> I think that this really belongs in core. Now that trunk has moved to
>>> 3.0 and we will have a new 2.1 branch (when we decide to cut it from
>>> 2.0.10 or 2.0.9...not sure where the current one came from), this would
>>> be perfect to fit in as a
>Yes, the 2.1 (or 3.0?) that will get these changes in the core is not
>around the corner yet, so I think having the fuctionality now is
>beneficial for maven users in general.
2.1 can come out as soon as we want it to, it's only blocked by 2.0.10
so we can cut the branch.
---
On Thu, 2008-08-14 at 20:37 -0700, Dan Fabulich wrote:
> I've checked in a new plugin to the sandbox called the "Maven Reactor
> Plugin". You can use it to build a subset of interdependent projects in a
> reactor. It should be useful in large reactor builds that include
> irrelevant stuff you
this really belongs in core. Now that trunk has moved to
>>> 3.0 and we will have a new 2.1 branch (when we decide to cut it from
>>> 2.0.10 or 2.0.9...not sure where the current one came from), this would
>>> be perfect to fit in as a new feature. I don't want the new
be perfect to fit in as a new feature. I don't want the new 2.1.0 to
grow into a monster so for example we could implement this and release
it, then we could add the parallel download and release as 2.2 etc.
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Thu
from), this would
be perfect to fit in as a new feature. I don't want the new 2.1.0 to
grow into a monster so for example we could implement this and release
it, then we could add the parallel download and release as 2.2 etc.
-Original Message-----
From: Dan Fabulich [mailto:[EMAIL PROTEC
ownload and release as 2.2 etc.
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2008 8:38 PM
To: Maven Users List; Maven Developers List
Subject: New sandbox plugin: maven-reactor-plugin
I've checked in a new plugin to the sandbox called the &q
as 2.2 etc.
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2008 8:38 PM
To: Maven Users List; Maven Developers List
Subject: New sandbox plugin: maven-reactor-plugin
I've checked in a new plugin to the sandbox called the "Maven Reactor
Plugin&
I've checked in a new plugin to the sandbox called the "Maven Reactor
Plugin". You can use it to build a subset of interdependent projects in a
reactor. It should be useful in large reactor builds that include
irrelevant stuff you're not working on.
It includes the following goals:
reacto
14 matches
Mail list logo
