It's not _so_ bad as he isn't inheriting from the aggregator pom, so in effect the dependency forces the aggregator to be built last...
Generally a bad practice, and Maven will blow up if you use the aggregator as a parent for the child, but in this case he can get away with it (until he hits his problem...) On 13 March 2013 15:58, Wayne Fay <[email protected]> wrote: > > <dependencies> > > <dependency> > > <groupId>maven.issue</groupId> > > <artifactId>dependency</artifactId> > > <version>1.0</version> > ... > > <modules> > > <module>dependency</module> > > </modules> > > This seems like a bad idea right up front. You shouldn't have a > dependency as a module in the same pom. You have constructed > essentially a circular reference. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
