This document describes the supplied goals that are available when using the J2EE Plug-in with Maven.
Please refer to the Integration document for more information on how to integrate these goals into your project.
The build file utilizes various properties for default and user-configurable settings. All J2EE Plug-in properties are described in the Properties document. The rest of this document assumes your project follows the standard Directory Layout; however, it is possible to override many of these defaults.
j2ee:validate-war target validates the newly
produced war file.
The validator checks the folowing:
<servlet>tag are loadable from the war file and not the classpath
<servlet>tag exist in the war
<taglib-location>that exists in the war
<location>nested within an
<error-page>element must exist in the war file
<form-login-config >element must exist in the war file
j2ee:ejb target generates the
ejb jar file
for the project. Optionally it can also create jars containing the local
and remote interfaces. The files are produced in the
directory and have a name based on the
The files generated are:
Maven also includes the license file, LICENSE.txt, if it exists, in the META-INF directory.
The contents of the ejb file include:
A J2EE enterprise bean deployment descriptor, which
is placed in the root of the resulting ear file.
The files in the
Files to be included the
Maven also includes the license file, LICENSE.txt, if it exists, under the directory META-INF.
The contents of the ear file include:
A J2EE enterprise application deployment descriptor, which
is placed in the META-INF of the resulting ear file.
Any dependencies specified in your
<dependency> <id>CustomerEjb</id> <version>2.4</version> <properties> <ear.bundle.jar>true</ear.bundle.jar> </properties> </dependency>