------ Predefined Assembly Descriptors ------ Johnny R. Ruiz III Edwin Punzalan John Casey ------ 2011-02-07 ------ ~~ Licensed to the Apache Software Foundation (ASF) under one ~~ or more contributor license agreements. See the NOTICE file ~~ distributed with this work for additional information ~~ regarding copyright ownership. The ASF licenses this file ~~ to you under the Apache License, Version 2.0 (the ~~ "License"); you may not use this file except in compliance ~~ with the License. You may obtain a copy of the License at ~~ ~~ http://www.apache.org/licenses/LICENSE-2.0 ~~ ~~ Unless required by applicable law or agreed to in writing, ~~ software distributed under the License is distributed on an ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY ~~ KIND, either express or implied. See the License for the ~~ specific language governing permissions and limitations ~~ under the License. ~~ NOTE: For help with the syntax of this file, see: ~~ http://maven.apache.org/doxia/references/apt-format.html Pre-defined Descriptor Files As of version 2.2, there are four predefined descriptor formats available for reuse, packaged within the Assembly Plugin, instead of the original three. Their descriptorIds are: %{toc|fromDepth=2|toDepth=2} * bin Use <<>> as the <<>> of your assembly-plugin configuration in order to create a binary distribution archive of your project. This built-in descriptor produces an assembly with the classifier <<>> in three archive formats: tar.gz, tar.bz2, and zip. The assembled archive contains the binary JAR produced by running <<>> plus any README, LICENSE, and NOTICE files available in the project root directory. Below is the <<>> descriptor format: %{snippet|id=bin|file=src/main/resources/assemblies/bin.xml} * jar-with-dependencies Use <<>> as the <<>> of your assembly-plugin configuration in order to create a JAR which contains the binary output of your project, along its the unpacked dependencies. This built-in descriptor produces an assembly with the classifier <<>> using the JAR archive format. Note that <<>> provides only basic support for uber-jars. For more control, use the {{{http://maven.apache.org/plugins/maven-shade-plugin/} Maven Shade Plugin}}. Below is the <<>> descriptor format: %{snippet|id=jar-with-dependencies|file=src/main/resources/assemblies/jar-with-dependencies.xml} * src Use <<>> as the <<>> in your assembly-plugin configuration to create source archives for your project. The archive will contain the contents of your project's <<>> directory structure, for reference by your users. The <<>> descriptorId produces an assembly archive with the classifier <<>> in three formats: tar.gz, tar.bz2, and zip. Below is the <<>> descriptor format: %{snippet|id=src|file=src/main/resources/assemblies/src.xml} * project (Since 2.2) Using the <<>> <<<\>>> in your Assembly Plugin configuration will produce an assembly containing your entire project, minus any build output that lands in the <<>> directory. The resulting assembly should allow your users to build your project using Maven, Ant, or whatever build system you have configured in your project's normal SCM working directory. It produces assemblies with the classifier <<>> in three archive formats: tar.gz, tar.bz2, and zip. The following is the assembly descriptor for the <<>> descriptorRef: %{snippet|id=project|file=src/main/resources/assemblies/project.xml}