On Tue, Oct 23, 2012 at 7:45 PM, Barrie Treloar <[email protected]> wrote: > On Wed, Oct 24, 2012 at 9:28 AM, Benson Margulies <[email protected]> > wrote: >> Barrie, >> >> We have an execution of the gmaven-plugin to set a property -- a >> property that we don't even need in the site build. >> >> I see: >> >> [INFO] --- gmaven-plugin:1.4:execute (default) @ tanuki-unpack --- >> >> and then a bunch of the usual, and then ... >> >> [INFO] >> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> [INFO] Forking Juggernaut Release Distribution 0.9.101-SNAPSHOT >> [INFO] >> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> >> The gmaven execution is bound to 'validate', which isn't even supposed >> to be in the site lifecycle as previously noted. >> >> Or, some of the Forking follows just after >> maven-javadoc-plugin:2.8.1:aggregate (aggregate) @ jug-setup-bt-root > > See > > http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html > > "Invokes the execution of the lifecycle phase generate-sources prior > to executing itself." > > So that's why verify is being run. > > I had this problem with enforcer bound to validate and being run > because of source:jar forking.
OK, that explains the forks, but not iterating infinitely in a loop forking the top of the build (and all the interior pieces). > > --------------------------------------------------------------------- > 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]
