[
https://issues.apache.org/jira/browse/MEAR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marek Gregor updated MEAR-227:
------------------------------
Description:
Currently includeInApplicationXml configuration option is available only for
jarModule:
https://maven.apache.org/plugins/maven-ear-plugin/modules.html#jarModule
We need to use it also for another module (in our case it is webModule). I
think it will be fine to enable this option for all modules (ejb, web, ...).
Motivation is to enable specific ear to be built with modules by default not
described in application.xml. Person responsible for deploying will add modules
to application.xml based on current case.
was:
Currently includeInApplicationXml configuration option is available only for
jarModule:
https://maven.apache.org/plugins/maven-ear-plugin/modules.html#jarModule
We need to use it also for another module (in our case it is webModule). I
think it will be fine to enable this option for all modules (ejb, web, ...).
> Configuration option includeInApplicationXml accesible for all modules
> ----------------------------------------------------------------------
>
> Key: MEAR-227
> URL: https://issues.apache.org/jira/browse/MEAR-227
> Project: Maven Ear Plugin
> Issue Type: Improvement
> Reporter: Marek Gregor
>
> Currently includeInApplicationXml configuration option is available only for
> jarModule:
> https://maven.apache.org/plugins/maven-ear-plugin/modules.html#jarModule
> We need to use it also for another module (in our case it is webModule). I
> think it will be fine to enable this option for all modules (ejb, web, ...).
> Motivation is to enable specific ear to be built with modules by default not
> described in application.xml. Person responsible for deploying will add
> modules to application.xml based on current case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
