Re: Plugin assembly: Howto use 'single' goal as an agregator ?

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

Re: Plugin assembly: Howto use 'single' goal as an agregator ?

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,

Re: Plugin assembly: Howto use 'single' goal as an agregator ?

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

Re: Plugin assembly: Howto use 'single' goal as an agregator ?

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

Re: Plugin assembly: Howto use 'single' goal as an agregator ?

Hi, If you like to produce a package (zip/tar/whatever kind of archive/bundle) which contains some modules/artifacts etc. from your multi module build it is 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

Plugin assembly: Howto use 'single' goal as an agregator ?

Hello, Since maven-assembly-plugin v3.3.0, the *attached* goal has been removed ( MASSEMBLY-704 ). This *attached* goal was an aggregator (v2.6 source