5774953683
- renamed property ejb.bundle.jar to ejb.bundle (old property is still supported but deprecated). This is compatible with war and ear plugins git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113598 13f79535-47bb-0310-9956-ffa450edef68
94 lines
2.8 KiB
XML
94 lines
2.8 KiB
XML
<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
<document>
|
|
|
|
<properties>
|
|
<title>Properties</title>
|
|
<author email="nathan.coast@blueyonder.co.uk">Nathan Coast</author>
|
|
</properties>
|
|
|
|
<body>
|
|
<section name="ejb jar settings">
|
|
<table>
|
|
<tr><th>Property</th><th>Optional?</th><th>Description</th><th>Default</th></tr>
|
|
<tr>
|
|
<td>maven.ejb.src</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Root of files to be included within the ejb-jar. The same directory structure will be followed within the assembled jar file.
|
|
</td>
|
|
<td>
|
|
src/ejb
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.ejb.manifest</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Location of the manifest file to be used within the ejb jar file.
|
|
</td>
|
|
<td>
|
|
${maven.ejb.src}/META-INF/MANIFEST.MF
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</section>
|
|
<section name="other settings">
|
|
<table>
|
|
<tr><th>Property</th><th>Description</th><th>See</th></tr>
|
|
<tr>
|
|
<td>maven.build.dir</td>
|
|
<td>where the comonent will be assembled</td>
|
|
<td>
|
|
<A href="../../../java/target/docs/properties.html#Other Settings">maven.build.dir</A>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.final.name</td>
|
|
<td>The assembled component will be <code>${maven.build.dir}/${maven.final.name}.jar</code></td>
|
|
<td>
|
|
<A href="../../../java/target/docs/properties.html#Other Settings">maven.final.name</A>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</section>
|
|
<section name="Including Jars in standalone ejb jars">
|
|
<p>
|
|
You must tell Maven what jars you want included in the ejb. This is
|
|
probably only needed if you are building a standalone ejb jar. This
|
|
is achieved by specifying meta-information in the POM, using the
|
|
following syntax:
|
|
</p>
|
|
|
|
<source><![CDATA[
|
|
<dependency>
|
|
<id>jarid</id>
|
|
<version>jarversion</version>
|
|
<properties>
|
|
<ejb.bundle>true</ejb.bundle>
|
|
</properties>
|
|
</dependency>
|
|
]]></source>
|
|
|
|
</section>
|
|
<section name="Generating the manifest Class-Path entry">
|
|
<p>
|
|
To access the classes within other jars (either within the same
|
|
ear file or embedded within the same ejbjar), you will need to
|
|
use the manifest Class-Path entry. To generate the classpath
|
|
for an ejb-jar from the dependencies use this syntax.
|
|
</p>
|
|
|
|
<source><![CDATA[
|
|
<dependency>
|
|
<id>jarid</id>
|
|
<version>jarversion</version>
|
|
<properties>
|
|
<ejb.manifest.classpath>true</ejb.manifest.classpath>
|
|
</properties>
|
|
</dependency>
|
|
]]></source>
|
|
|
|
</section>
|
|
</body>
|
|
</document>
|