You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Dain Sundstrom <ds...@gluecode.com> on 2004/10/05 21:50:40 UTC
Important: maven command line options
I'm thinking about using the maven multiproject plugin as replacement
for our current reactor build. Before I do this, I'd like to know
which options of our current build people are using...
Are you using any of the following command line options
module.types Comma seperated list of module types (ie. specs or
modules)
module.includes Comma seperated list of module names (ie. common,
core, ...)
modules Same as module.includes, module.includes initializes
to this value
module.excludes Comma seperated list of module names to exclude
Also if you are using anything off the beaten path let me know.
Thanks,
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
Re: Important: maven command line options
Posted by Dain Sundstrom <ds...@gluecode.com>.
On Oct 5, 2004, at 1:56 PM, Aaron Mulder wrote:
> This is a little off topic, but it would be nice to have a target
> that does nothing but update any third-party libraries that have
> changed,
> so you could run that once and then do maven -o instead of having to
> run
> maven online and have it attempt to download the same libraries dozens
> of
> times each -- and worse yet, if the build fails, you need to run online
> next time too because you never know if it got all the updates before
> it
> died.
Great idea. Can you add a JIRA issue and assign it to me?
> Anyway, as far as the real question goes, I use -Dmodules=...
> sometimes but it wouldn't break my heart if I had to change to the
> appropriate directory and run maven there instead.
I'm going to try to support that one.
-dain
Re: Important: maven command line options
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
This is a little off topic, but it would be nice to have a target
that does nothing but update any third-party libraries that have changed,
so you could run that once and then do maven -o instead of having to run
maven online and have it attempt to download the same libraries dozens of
times each -- and worse yet, if the build fails, you need to run online
next time too because you never know if it got all the updates before it
died.
Anyway, as far as the real question goes, I use -Dmodules=...
sometimes but it wouldn't break my heart if I had to change to the
appropriate directory and run maven there instead.
Aaron
On Tue, 5 Oct 2004, David Blevins wrote:
> On Tue, Oct 05, 2004 at 12:50:40PM -0700, Dain Sundstrom wrote:
> > I'm thinking about using the maven multiproject plugin as replacement
> > for our current reactor build. Before I do this, I'd like to know
> > which options of our current build people are using...
> >
> > Are you using any of the following command line options
> >
> > module.types Comma seperated list of module types (ie. specs or
> > modules)
> > module.includes Comma seperated list of module names (ie. common,
> > core, ...)
> > modules Same as module.includes, module.includes initializes
> > to this value
> > module.excludes Comma seperated list of module names to exclude
> >
>
> I use -Dmodules=foo,bar,assembly on a fairly regular basis.
>
> You trying to figure out which ones are worth the pain of adding to multiproject?
>
Re: Important: maven command line options
Posted by Dain Sundstrom <ds...@gluecode.com>.
On Oct 5, 2004, at 1:39 PM, David Blevins wrote:
> On Tue, Oct 05, 2004 at 12:50:40PM -0700, Dain Sundstrom wrote:
>> I'm thinking about using the maven multiproject plugin as replacement
>> for our current reactor build. Before I do this, I'd like to know
>> which options of our current build people are using...
>>
>> Are you using any of the following command line options
>>
>> module.types Comma seperated list of module types (ie. specs or
>> modules)
>> module.includes Comma seperated list of module names (ie. common,
>> core, ...)
>> modules Same as module.includes, module.includes initializes
>> to this value
>> module.excludes Comma seperated list of module names to exclude
>>
>
> I use -Dmodules=foo,bar,assembly on a fairly regular basis.
>
> You trying to figure out which ones are worth the pain of adding to
> multiproject?
Yes.. the good news is I think that is the easy one to implement :)
-dain
Re: Important: maven command line options
Posted by David Blevins <da...@visi.com>.
On Tue, Oct 05, 2004 at 12:50:40PM -0700, Dain Sundstrom wrote:
> I'm thinking about using the maven multiproject plugin as replacement
> for our current reactor build. Before I do this, I'd like to know
> which options of our current build people are using...
>
> Are you using any of the following command line options
>
> module.types Comma seperated list of module types (ie. specs or
> modules)
> module.includes Comma seperated list of module names (ie. common,
> core, ...)
> modules Same as module.includes, module.includes initializes
> to this value
> module.excludes Comma seperated list of module names to exclude
>
I use -Dmodules=foo,bar,assembly on a fairly regular basis.
You trying to figure out which ones are worth the pain of adding to multiproject?