Message:
The following issue has been closed.
Resolver: Felipe Leme
Date: Mon, 8 Nov 2004 11:27 PM
Closing issue then...
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPEAR-22
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPEAR-22
Summary: The ear plugin needs to have a settable manifest Class-Path like
the WAR plugin
Type: New Feature
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-ear-plugin
Fix Fors:
1.6
Assignee: Felipe Leme
Reporter: Wiley Fuller
Created: Wed, 13 Oct 2004 7:27 PM
Updated: Mon, 8 Nov 2004 11:27 PM
Description:
There is currently no way to add bundled dependencies to the Class-Path entry
in the EAR manifest file, like in the WAR plugin.
A dependency entry in the project file should look like the following...
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.8</version>
<properties>
<ear.bundle>true</ear.bundle>
<ear.manifest.classpath>true</ear.manifest.classpath>
</properties>
</dependency>
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
