Yeah, I just wanted to show one example. The point is that install mojo is not invoked for all projects in the build, as expected, and will never kick in to install the accumulated projects:
https://github.com/apache/maven-plugins/blob/8678f791e717c14f6b91b80fade0a376ac87625a/src/main/java/org/apache/maven/plugin/install/InstallMojo.java#L116 Again, aggregator is just one possible reason. On Fri, Feb 28, 2014 at 12:36 PM, Karl Heinz Marbaise <[email protected]>wrote: > Hi, > > > > Install at end of m-install-p has problems related to aggregator POMs > >> for example, here is an example plugin that will NOT install anything >> than the aggregator POM (attached). >> > If you change that project into a multi -module build it will work. > > An aggregator is something different than a multi-module build... > > I'm tlaking about a multi-module build... > > > Kind regards > Karl-Heinz Marbaise > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
