Thanks Robert, Karl, I created a JIRA MNG-6336 here:
https://issues.apache.org/jira/browse/MNG-6336
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
-
To unsubscribe, e-mail:
Based on the current requirement as described by Karl Heinz there seems to
be room for it.
I don't expect this to be part of Maven3, but we have more lifecycle
related improvements planned for a next major[1].
Just create the issue as an improvement, and let's see what the impact
will be.
Thanks Robert, that makes sense. At least it explains why aggregator will not
work in my case.
Do you think my case is not so uncommon and I should open a bug, or I
misunderstood "the Maven way" and have to adapt ?
Regards
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
IIUC the aggregator only works when calling a goal directly, not as part
of the lifecycle.
That's why release:prepare / release:perform works
I can't think of a plugin that is part of the lifecycle AND which act as
an aggregator.
thanks,
Robert
On Mon, 08 Jan 2018 14:25:36 +0100,
Thanks for your response Hervé,
I've made a sample plugin here:
https://github.com/fmarot/print-dummy-maven-plugin
When included in the "" section of a parent pom of a
multimodule Maven project, the behavior is shown: when running 'mvn
validate', "dummy" is printed for for each and every child
Hi François,
Happy New Year!
Can you check in generated META-INF/maven/plugin.xml descriptor that your
annotation in source was well detected?
Because it looks like a typo somewhere in your plugin: if you can share the
code (eventually privately), perhaps new eyes can find it.
Regards,
[Sorry, re-posting with correct formatting]
Hi all & happy new year !
I have a question regarding plugin development.
I have made a custom plugin and would like to make it's Mojo executed once
*and only once* in my whole reactor build. If I include it in my parent pom
(not in pluginManagement),
Hi all & happy new year !I have a question regarding plugin development.I
have made a custom plugin and would like to make it's Mojo executed once
*and only once* in my whole reactor build.If I include it in my parent pom
(not in pluginManagement), then by default it is executed once at the root
