[ http://jira.codehaus.org/browse/MEAR-26?page=all ] Stephane Nicoll closed MEAR-26: -------------------------------
Resolution: Fixed OK, implemented, see doc for more details the following will map the my-rar packaging to the standard rar packaging. {code:xml} <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ear-plugin</artifactId> <configuration> <artifactTypeMappings> <artifactTypeMapping type="my-rar" mapping="rar"/> </artifactTypeMappings> </configuration> </plugin> </plugins> </build> {code} > Ability to configure and use custom artifact types > -------------------------------------------------- > > Key: MEAR-26 > URL: http://jira.codehaus.org/browse/MEAR-26 > Project: Maven 2.x Ear Plugin > Type: New Feature > Reporter: Stephane Nicoll > Assignee: Stephane Nicoll > Fix For: 2.2 > > > Users are creating custom artifact types (such as company-jar, my-rar, > whatever) and needs to use them with the EAR plugin. Currently the EAR plugin > only recognizes the "standard" artifact types: jar, ejb, ejb-client, war, > rar, sar, wsr. > This needs to be extended to allow any custom artifact types to be bound to > this type. > Configuration would be as follows: > {code:xml} > <configuration> > <customArtifactTypes> > <customArtifactType> > <type>my-rar</type> > <mapping>rar</mapping> > </customArtifactType> > </customArtifactTypes> > </configuration> > {code} > The config above maps the {{my-rar}} custom artifact type to the standard > {{rar}} type. This means that my-rar artifact will be handled as a standard > rar by the EAR plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira