Repository navigation
[MEAR-227] Configuration option includeInApplicationXml accessible for all modules #398
Description
Marek Gregor opened MEAR-227 and commented
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.
No further details from MEAR-227
Activity
jira-importer commentedon Oct 8, 2022
Slawomir Jaranowski commented
I as see the standard module was added to
application.xmlby default.Can you retest with the latest version of
m-ear-pelharo commentedon Jul 28, 2026
per Gemini:
If you look closely at the current API and documentation for the latest maven-ear-plugin (version 3.4.0), the includeInApplicationXml property is still explicitly restricted to JarModule. It is not present in the base AbstractEarModule class, meaning you still cannot configure this property for a webModule, ejbModule, or any other standard Java EE module.
The standard behavior of the plugin isâand always has beenâto automatically include standard modules (like WARs and EJBs) in the generated application.xml. However, the original reporter's goal was the exact opposite: they wanted the ability to package a webModule inside the EAR without it being automatically written into the application.xml. They wanted the toggle exposed for all modules so they could set includeInApplicationXml=false, leaving the deployment team to manually configure the XML based on the specific deployment environment.
Because standard modules still lack this configuration toggle and cannot be omitted from the generated deployment descriptor without being entirely excluded from the EAR archive, the issue remains a valid, unresolved feature request.