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
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
- 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
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
