Hello,
Even if using aggregator is not a good practice in this case ... if there
is a technical possibility to force the aggregation for a goal by pom
configuration, I'll take it.
Because after continuing to dig, I am in a dead-end ^^
Many thanks.
Best regards
2017-03-14 10:45 GMT+01:00 Alix
Hi Curtis,
Why not stick with the old version of maven-assembly-plugin until you have
> to refactor your build more thoroughly?
>
I thought to that, but it collides another (philosophical) concept: to use
always the last version of plugins ! ^^
More seriously and to explain, the "problem" is
Hi Alix,
Why not stick with the old version of maven-assembly-plugin until you have
to refactor your build more thoroughly?
Regards,
Curtis
--
Curtis Rueden
LOCI software architect - https://loci.wisc.edu/software
ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden
On Tue, Mar 14,
Hi,
as it seems, wrong or misspelled configuration options (i.e. those which
can not be set on Mojos as @Parameters because there is no parameter of
this name) are simply ignored for Maven 3.3
IMO this is a dangerous behavior as of course there _was_ some intention
from the user to put this
Hi Karl Heinz,
Thanks for your answer (and sorry for mine late).
the best thing to create a separate module in your build with packaging pom
> and only put the maven-assembly-plugin in it and bind it to the life cycle
> This is simply a good way of following single responsibility principle.
>
