| Property | Optional? | Description | Default |
|---|---|---|---|
| maven.ear.manifest | Yes | Location of the manifest file to be used within the ear file. | src/application/META-INF/MANIFEST.MF |
| maven.j2ee.ear.appxml | Yes | Location of the application.xml file to be used within the ear file. | src/application/META-INF/application.xml |
| maven.j2ee.ear.appxml.generate | Yes | Indicates if application.xml files should be autogenerated | false |
| maven.ear.displayname | Yes | Display name of the application to be used when application.xml file is autogenerated | ${pom.id} |
| Property | Description | See |
|---|---|---|
| maven.build.dir | where the component will be assembled | maven.build.dir |
| maven.final.name | The assembled component will be ${maven.build.dir}/${maven.final.name}.ear |
maven.final.name |
You must tell Maven what artifact you want to include in the ear. This operation is type sensitive. Maven can bundle in ear artifacts of following types: jar, war, ejb. Artifacts of other types are ignored. This is achieved by specifying meta-information in the POM, using the following syntax:
Those artifact will be also "visible" during generation of application.xml file. In case of war artifacts you can also specify context root which will be set in application.xml file: