Just make sure you done deploy this "extra" aggregating pom, or make sure you use a different artifactId. I strongly suggest not deploying it as it would be your private special build purposes agg pom. Thus, don't make it a parent pom.
/Anders On Fri, May 11, 2012 at 10:30 PM, KARR, DAVID <dk0...@att.com> 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, >> >> Why not just create a new pom file at level1, rather than modifying an >> existing one? >> >> Something like this in pom-david-karr.xml: >> >> <project> >> <!-- snip --> >> <modules> >> <module>level2</module> >> <module>level2/level3</module> >> </modules> >> </project> >> >> Then, you just use the -f command line argument to get Maven to use a >> different POM file. >> >> mvn -f pom-david-karr.xml > > Ah. I had considered creating a custom and separate pom at the level where > we had the additional module, but I didn't think of having this at the top > level, to specify a module below the level of the first child. I believe > this could work also. > >> -----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.com/EmailSecurity/IDSP.html for more >> information. >> >> > -----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 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 make this work in Ant if you couldn't >> > change the build.xml file? Or a similar change with make if you >> > couldn't change the makefile? >> >> It's only silly and arbitrary if you don't know the circumstances. In >> this case, it's a reasonable compromise, and I'll leave it at that. >> >> I can get this to work by simply having the build script manually run >> the omitted module in the child module. >> >> Thanks anyway. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
