If the Assembly Plugin is run during the package phase, do my assemblies get deployed during the deploy phase?

Yes. The assemblies created by the Assembly Plugin is attached to your project so it gets deployed too.


Can I use an artifact created by the assembly plugin as a dependency?

Yes. You can refer to it using the id of the assembly as the dependency classifier.


How do I use the Assembly Plugin to package my project's javadoc files?

The Javadoc Plugin can generate the javadoc files of your projects. Also, the Javadoc Plugin can package them!

Please see the Javadoc Plugin Documentation.


Starting with version 2.2 configuration/executions defined in a parent POM are no longer inherited, why?

As part of the deprecation of all goals except for the single goal, the goals of the Assembly Plugin and their configuration/executions are no longer inherited by default.

If you need the configuration/executions to be inherited you need to explicitly say so by adding a line to the plugin declaration in the parent POM:



In previous versions (before 2.2 final), I followed the example in the documentation for sharing assembly descriptors, which recommended using the <descriptors/> configuration section to refer to the shared assembly descriptor. As of version 2.2, this no longer works. Why not?

The use of <descriptors/> was always incorrect, and counter to the design of this configuration parameter. Unfortunately, some code was introduced in version 2.2-beta-2 that allowed this parameter to reference descriptors on the classpath, instead of being forced to use <descriptorRefs/> as is the intention of the design. In version 2.2, this bug was fixed.

It is important to note that the correct form, <descriptorRefs/> has always worked, and continues to work. The documentation has now been fixed to reflect the correct configuration.


The Assembly Plugin is saying it cannot find files for the module binaries included by my assembly descriptor. What gives?

If your assembly includes module binaries, those binaries won't be available to the assembly plugin except in special cases. This is normally seen when the Assembly Plugin is bound to a phase of the standard build lifecycle in the parent POM of a multimodule build. It is a result of the way Maven sorts and executes the build process for a multimodule project layout.

In a multimodule hierarchy, when a child module declares the parent POM in its <parent/> section, Maven interprets this to mean that the parent project's build must be completed before the child build can start. This ensures that the parent project is in its final form by the time the child needs access to its POM information. In cases where the Assembly Plugin is included as part of that parent project's build process, it will execute along with everything else as part of the parent build - before the child build can start. If the assembly descriptor used in that parent build references module binaries, it effectively expects the child build to be completed before the assembly is processed. This leads to a recursive dependency situation, where the child build depends on the parent build to complete before it can start, while the parent build depends on the presence of child-module artifacts to complete successfully. Since these artifacts are missing, the Assembly Plugin will complain about missing artifacts, and the build will fail.

In many cases, you can avoid this problem by adding a new child module whose sole purpose is to produce your assembly. In the POM for this new project, add dependency definitions for any of the module binaries you had previously referenced. This will ensure the new assembly child is built last. Then, move your assembly descriptor into this new child module. At this point, you have the option of either changing all moduleSet/binaries references to dependencySet references, or you can keep the moduleSets and instead set the useAllReactorProjects flag to true for each moduleSet.

Obviously, any fileSet or file references you may have in this descriptor may need to be adjusted or have the files they reference moved into the new child module alongside the descriptor itself.

In cases where you absolutely must use module-binaries references, you should create an assembly-child POM mentioned above, then insert <useAllReactorProjects>true</useAllReactorProjects> to each of your moduleSet sections. Then, bind the assembly in your assembly-child POM (normally to the package phase) using the single goal. When you execute the build from the top-level POM, Maven should generated your assembly in the new child project.

NOTE: The useAllReactorProjects flag is only available in version 2.2 and higher.


In previous versions (before 2.2 final), leaving off the assembly id and leaving the classifier unconfigured resulted in the assembly being used as the project's main artifact. With the 2.2 release, this configuration results in a validation error. My project depended on the previous behavior! Why has this changed, and how can I make this work in my project?

The assembly id is used for reporting and calculating descriptor/component merges. They're also required to avoid collisions with the main output of the project's build process. It's critical that this id be in place, to overriding the project's main artifact inadvertently, and to help error-reporting make sense to the user. Leaving off the assembly id has always been an error, but unfortunately previous releases contained a bug in the model that allowed empty or missing assembly id's. This bug has been fixed in version 2.2.

However, in certain cases it makes sense to use the assembly output as the main project artifact. So, what's the correct approach in these situations? This use case is meant to require deliberate configuration, so your intention to depart from the normal behavior will be clear. To configure the use of the assembly output as the main project artifact, follow these steps:

  1. Make sure your assembly only uses one format. More than one format could mean the assembly artifact used for the project's main artifact is non-deterministic.
  2. Add the configuration: <appendAssemblyId>false</appendAssemblyId> to your assembly-plugin execution. This will prevent the assembly artifact from simply being attached to the project.


I have a dependencySet that includes some artifacts with classifiers, and others without classifiers. How can I setup the file mappings to handle both cases appropriately?

The best way to handle a mixed bag of dependencies with and without classifiers is to use the ${dashClassifier?} expression, added in version 2.2-beta-2 of the assembly plugin especially for this purpose. This expression will determine whether each artifact has a classifier, and if it does, it will substitute the artifact's classifier - prepended by a dash - in place of the expression.

For example, suppose you want to include two artifacts, commons-logging-1.0.4.jar, and yourserver-1.0-client.jar (where 'client' is the classifier of the second artifact). To do this, simply add the following to your dependencySet:



Which properties can be used in the outputFileNameMapping parameter.

You can use :

  • all system or maven properties available in your build with the syntax ${myProperty}.
  • all environment variables with ${env.XXX} where XXX is the environment variable.
  • the special ${dashClassifier?} property (see above).
  • all artifacts attributes ( from the Artifact class) like :
    • ${artifact.groupId} : The artifact groupId.
    • ${artifact.artifactId} : The artifact artifactId.
    • ${artifact.version} : The artifact classifier.
    • ${artifact.baseVersion} : The artifact base version (For a SNAPSHOT it will be always -SNAPSHOT and not its timestamp even if you didn't built it yourself).
    • ${artifact.classifier} : The artifact classifier.
    • ${artifact.scope} : The artifact scope.
    • ${artifact.groupIdPath} : The groupId of the artifact as path
    • ${artifact.file.name} : The name of the file attached to this artifact
    • ...
    You can use ${module.XXXXX} when using it for your project modules artifacts.


Tar complains about groupid value being too big

GNU tar has restrictions on max value of UID/GUID in tar files. Consider using the more well defined POSIX tar format, which should support larger values. Use tarLongFileMode=posix in the assembly:single goal.