R, DAVID wrote:
>> -Original Message-
>> From: GALLAGHER, RON
>> Sent: Friday, May 11, 2012 11:58 AM
>> To: Maven Users List
>> Subject: RE: Some questions about customizing the build on the Maven
>> command line
>>
>> David,
>>
>
> -Original Message-
> From: GALLAGHER, RON
> Sent: Friday, May 11, 2012 11:58 AM
> To: Maven Users List
> Subject: RE: Some questions about customizing the build on the Maven
> command line
>
> David,
>
> Why not just create a new pom file at level1, rathe
Ron Gallagher
-Original Message-
From: KARR, DAVID
Sent: Friday, May 11, 2012 11:51 AM
To: Maven Users List
Subject: RE: Some questions about customizing the build on the Maven command
line
*** Security Advisory: This Message Originated Outside of AT&T ***.
Reference http://cso.att
> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com]
> Sent: Friday, May 11, 2012 7:31 AM
> To: Maven Users List
> Subject: Re: Some questions about customizing the build on the Maven
> command line
>
> >> Why can't you simply make level2
>> Why can't you simply make level2 a child (module) of level1, and the
>> same for level3 under level2? Why are you making things harder than it
>> needs to be?
>
> Because I can't change the poms.
Then you probably can't make this work. This is a silly and arbitrary
restriction. How would you ma
> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com]
> Sent: Thursday, May 10, 2012 7:24 PM
> To: Maven Users List
> Subject: Re: Some questions about customizing the build on the Maven
> command line
>
> > The directory that agg pom is in has an
> The directory that agg pom is in has an additional directory (call it
> "level3") that is not in
> the modules list, but is also a pom module. I have a basic idea of how I
> could specify a
> command line to run a build in "level2" that would build all the specified
> modules, and
> also buil
