Add the "addClasspath" element to your EAR/WAR/JAR plugin configuration:
<build>
.
.
<plugins>
.
.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
.
.
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
.
.
</configuration>
</plugin>
.
.
</plugins>
.
.
</build>
-----Original Message-----
From: ttjarl [mailto:[EMAIL PROTECTED]
Sent: Friday, March 24, 2006 5:01 AM
To: [email protected]
Subject: Manifest.mf Class-path
I have created a maven2 project with parent, EAR, WAR, EJB and a few JAR
POMs. There are also some dependencies and transitive dependencies.
I am not able to make maven generate the Class-path attribute in
manifest.mfin the jar-files.
What could I be doing wrong?
-jarl
This message and any attachments are confidential, proprietary, and may be
privileged. If this message was misdirected, Barclays Global Investors (BGI)
does not waive any confidentiality or privilege. If you are not the intended
recipient, please notify us immediately and destroy the message without
disclosing its contents to anyone. Any distribution, use or copying of this
e-mail or the information it contains by other than an intended recipient is
unauthorized. The views and opinions expressed in this e-mail message are the
author's own and may not reflect the views and opinions of BGI, unless the
author is authorized by BGI to express such views or opinions on its behalf.
All email sent to or from this address is subject to electronic storage and
review by BGI. Although BGI operates anti-virus programs, it does not accept
responsibility for any damage whatsoever caused by viruses being passed.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
