Custom Maven Assembly Descriptors: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
Custom assembly descriptors are conventionally placed under <tt>src/assembly</tt> of the module that executes the plugin. | Aside from [[https://kb.novaordis.com/index.php/Maven_assembly_Plugin#Pre-defined_Assembly_Descriptors]], Maven allows creation of custom assembly descriptors. Custom assembly descriptors are conventionally placed under <tt>src/assembly</tt> of the module that executes the plugin. | ||
=Example= | =Example= | ||
Revision as of 18:56, 7 November 2016
External
- Custom assembly descriptor reference http://maven.apache.org/components/plugins/maven-assembly-plugin/assembly.html
Internal
Overview
Aside from [[1]], Maven allows creation of custom assembly descriptors. Custom assembly descriptors are conventionally placed under src/assembly of the module that executes the plugin.
Example
This is an example of a custom assembly descriptor, used to build a complex release artifact for a multi-module project:
Elements
Assembly ID
The assembly ID is specified as the value of the <id> element in the assembly descriptor. The assembly ID will become the assembly artifact classifier, present between the version and the extension. The artifact will be named <project-name>-<assemblyId>.<ext>. If I just want it to be <project-name>.<ext> (or <final-name>.<ext>), do not use an <id>...</id> declaration in the assembly descriptor.