Yes. I also tried adding the <inherited> tag with the plugin defined in the <build> section (not as a profile). I got the same result. The children still executed the plugin. I defined it to execute on the deploy phase.
Stephen Connolly wrote: > Are you saying that if you do sth like this: > > <project> > ... > <profiles> > ... > <profile> > <id>changes-report</id> > <activation> > ... > </activation> > <build> > <plugins> > <plugin> > <groupId>...</groupId> > <artifactId>...</artifactId> > <version>...</version> > <inherited>false</inherited> > <executions> > <execution> > <id>produce-changes-report</id> > <phase><!-- I don't know where you want this, either > -->site<!-- or -->deploy</phase> > <goals> > <goal>do-the-changes-report-mojo</goal> > </goals> > <configuration> > ... > </configutation> > </execution> > </executions> > </plugin> > </plugins> > </build> > </profile> > ... > </profiles> > ... > </project> > > That the plugin gets executed in the child modules.... or have you been > trying to run the mojo from the CLI rather than integrating it into the > lifecycle > > -Stephen > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
