You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2015/11/04 17:31:27 UTC
[jira] [Updated] (MEAR-161) Accept custom EarModule implementations
[ https://issues.apache.org/jira/browse/MEAR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise updated MEAR-161:
-------------------------------------
Fix Version/s: (was: waiting-for-feedback)
> Accept custom EarModule implementations
> ---------------------------------------
>
> Key: MEAR-161
> URL: https://issues.apache.org/jira/browse/MEAR-161
> Project: Maven Ear Plugin
> Issue Type: Improvement
> Reporter: Harvey Raja
>
> It would be great if the plugin allowed users to specify custom EarModule, i.e. a Map configuration parameter with key being module type and value being the EarModule class implementation. This would allow any module types not specified in the jee spec to be supported by the plugin by vendors providing their own implementations. Additionally this could result in the generation of a container specific descriptor file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)