ok: it's good to have a workaround I'm interested in working on a real world scenario, without multi- module/aggregate, since aggregate will be a harder case
do you have something public to show the problem? Regards, Hervé Le samedi 23 août 2014 07:38:47 Michael Norman a écrit : > For now, I have solved our problem of duplicate phase execution by > commenting-out the reporting > stanza's of our pom file. > > Everything we need is produced by goals other than 'site' - except > findbugs. For that, we are now > making an explicit call to 'findbugs:check' (bound to 'verify') which > doesn't seem to have > the 'forked-duplication' problem. > > All of our reports are being generated post-build by Jenkins, so everything > is working. > > Thanks, > > Mike > > > > On Fri, Aug 22, 2014 at 8:25 AM, Hervé BOUTEMY <herve.bout...@free.fr> > > wrote: > > - use Maven 3.2.2 at least: MNG-5630 will really help you understand > > - if not possible, use m-site-p 3.4: MSHARED-333 does something quite > > equivalent and doesn't require a specific Maven version > > > > and you can read MJAVADOC-171, where I managed to analyze the problem > > (quite > > recently...) and explained it as much as possible > > > > > > in summary, there is a problem with forked lifecycles launched by plugins > > executed from m-site-p (which gets even bigger when run in aggregated > > mode): I > > now understand the problem, given previous analysis (which took me a few > > years > > of thinking/trying/...), but I still didn't have time to work on a fix > > > > If you're interested on working with me on this, I'll be happy to have > > someone > > with me > > > > Regards, > > > > Hervé > > > > Le jeudi 21 août 2014 22:53:03 Michael Norman a écrit : > > > I have a simple Maven project (a web-app) that uses the ' > > > frontend-maven-plugin' > > > to handle various Javascript-related chores (installing node, running > > > Grunt, Karma etc.) > > > > > > Unfortunately, the frontend stuff runs twice on a 'mvn clean site' > > > > command > > > > > - when > > > I turned on debug-output (in Eclipse) I can "see" the reactor list 2 > > > > calls > > > > > to the frontend plugin. > > > > > > Is there any techniques or help anyone can suggest to try to figure out > > > what is causing > > > the extra execution? > > > > > > Thanks in advance, > > > --- > > > Mike Norman > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
