You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 12:03:00 UTC

[jira] [Updated] (MEAR-227) Configuration option includeInApplicationXml accessible for all modules

     [ https://issues.apache.org/jira/browse/MEAR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold updated MEAR-227:
---------------------------------------
    Summary: Configuration option includeInApplicationXml accessible for all modules  (was: Configuration option includeInApplicationXml accesible for all modules)

> Configuration option includeInApplicationXml accessible 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
>            Priority: Major
>
> 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, ...). The 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
(v8.3.4#803005)