Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add extensions to lifecycle doco 

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@292173 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Leslie Porter 2005-09-28 13:12:30 +00:00
parent 826f3e2a86
commit 8fa3a0922a
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
maven-site/src/site/apt/lifecycle.apt
View File

@ -269,8 +269,23 @@ m2 clean:clean install
The phases to bind are listed in the configuration element, and each that is given can have one goal associated with
that phase for that particular packaging.
Once this is included in the JAR and the plugin is added to the project, the packaging will also be available from
that project.
Once this is included in the JAR, the plugin needs to be added to the project to make the packaging available from
that project. In addition to listing the plugin, you must specify that it provides extensions:
----
...
<packaging>plexus-application</packaging>
...
<plugin>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-maven-plugin</artifactId>
<extensions>true</extensions>
</plugin>
...
----
Setting the extensions flag is also necessary if you provide custom artifact type handlers (closely related to
providing a packaging).
** Forking a Parallel Lifecycle