This plugin generates Java EE Enterprise Archive (EAR) file. It can also generate the deployment descriptor file (e.g. application.xml).
The EAR plugin supports the following artifacts:
For available configuration options for these artifacts, please see the modules configuration.
For more information about the Java EE technology, please visit http://www.oracle.com/us/technologies/java/enterprise-edition/overview/index.html.
Starting with version 3.0.0 the usage of fileNameMapping has been removed. If you need to use a kind of file name mapping take a look at the new outputFileNameMapping which is more flexible.
EAR Plugin has two goals:
General instructions on how to use the EAR Plugin can be found on the usage page. Some more specific use cases are described in the examples given below. Further real-life examples are given in the plugin's test suite.
In case you still have questions regarding the plugin's usage, please have a look at the FAQ and feel free to contact the user mailing list. The posts to the mailing list are archived and could already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching the mail archive.
If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our issue tracker. When creating a new issue, please provide a comprehensive description of your concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason, entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated. Of course, patches are welcome, too. Contributors can check out the project from our source repository and will find supplementary information in the guide to helping with Maven.
To provide you with better understanding on some usages of the EAR Plugin, you can take a look into the following examples: