You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2006/04/09 10:50:48 UTC
[jira] Updated: (MEAR-26) Ability to configure and use custom
artifact types
[ http://jira.codehaus.org/browse/MEAR-26?page=all ]
Stephane Nicoll updated MEAR-26:
--------------------------------
Description:
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.
was:
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>
</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.
> 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
> 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