Hello, Since maven-assembly-plugin v3.3.0, the *attached* goal has been removed ( MASSEMBLY-704 <https://issues.apache.org/jira/browse/MASSEMBLY-704>).
This *attached* goal was an aggregator (v2.6 source <https://svn.apache.org/repos/asf/maven/plugins/tags/maven-assembly-plugin-2.6/src/main/java/org/apache/maven/plugin/assembly/mojos/AttachedAssemblyMojo.java>) but not the *single* goal (v3.0.0 source <https://svn.apache.org/repos/asf/maven/plugins/tags/maven-assembly-plugin-3.0.0/src/main/java/org/apache/maven/plugins/assembly/mojos/SingleAssemblyMojo.java> ). Even *attached* goal "*leads to non-standard builds*", it was very useful on a multi modules project to generate a bundle with some modules items (artifacts, anything produced on *package* phase, ...) when the descriptor contains only *fileSets* definitions, using only one Maven command (e.g.: "*mvn install assembly:attached*") ; because assembly executed after package/install/deploy phase in each modules. With module binaries <https://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries> configuration, this job could be done ; but forces reviewing all assembly descriptors (usage of *moduleSet* in addition of *fileSet*), or using two steps Maven command. If you consider that using one command is a prerequisite ( *maven-release-plugin* plugin usage or some jobs with *maven-invoker*), the v2.x -> v3.x *maven-assembly-plugin* migration could be a little tricky. => Is there a way to execute single goal as an aggregator, via pom configuration (inheritable from a super/company parent pom) ? With that the *migration *could be just to replace *attached* by *single*. Many thanks in advance for tips or idea Best regards -- Alix Lourme
