> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Anders Hammar > Sent: Friday, March 09, 2012 1:13 PM > To: Maven Users List > Subject: Re: How to install the pom when it's also an aggregator? > > I don't follow. It shouldn't be a problem. What's the problem.
Ah, I think I just figured it out. It looks like it was just a bug in one of the parent poms. The snapshot version string it was specifying for its artifact didn't match the version specified in the child poms. Once I made them match, it started to build the thing. > It is possible to just build the "top pom" (mvn deploy -N), but this > should not be required. > On Fri, Mar 9, 2012 at 21:45, KARR, DAVID <[email protected]> wrote: > > I'm trying to build a project where the top-level POM is both a > parent POM and an aggregator. This seems like it sets up a chicken- > and-egg problem for the first build. How do I install the POM for the > top-level without trying to process the modules? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
