Assembly plugin: is it capable of working out for itself what artifacts it must include?

[Graham Leggett]

Hi all,

More questions about the assembly plugin.

According to the docs at http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html, it is implied that the assembly plugin is capable of working out for itself what the artifact is produced by a module.

      <includes>
        <include>org.test:child1</include>
      </includes>





[INFO] [assembly:directory-inline]

[ERROR] BUILD ERROR

[INFO] Trace


Regards,
Graham
--

All you need to do this tell the assembly plugin the name of the module, like this: The behaviour we are seeing however is that the assembly plugin cannot find the artifact, claiming the artifact does not exist. This would imply that the assembly plugin is not capable of working out for itself what artifact you are talking about, contrary to the documentation. In our case, the artifact when built has a classifier (eg macosx-ppc). Does the assembly plugin support the inclusion of modules containing artifacts with classifiers? [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] Included module: alchemy:alchemy-cdo:jar:4.0.6-SNAPSHOT does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. [INFO] ------------------------------------------------------------------------ org.apache.maven.lifecycle.LifecycleExecutionException: Included module: alchemy:alchemy-cdo:jar:4.0.6-SNAPSHOT does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)

smime.p7s
Description: S/MIME Cryptographic Signature