The following comment has been added to this issue:
Author: Michal Maczka
Created: Thu, 12 Feb 2004 6:18 AM
Body:
AFAIK usage of MANIFEST files in wars for "sharing" jars with other deployment units
of the j2ee application was not supported by j2ee 1.3 SPEC. That was the major reason
why this feature not never implemented in war plugin.
There were some application servers which allowed this. I don't know if it supported
in the uniform way.
I don't know how the situation looks like for j2ee 1.4.
Assuming that it was not yet "standardized" the question is:
should we take the pragmatic path and "help" users which might need this feature? I
think that yes as long as war plugin won't become specific for particular application
server.
Other thing is that IMHO It will be rather beneficial to let users generate their own
manifests files then introduce dozen of properties in POM and plugins for controlling
how does manifest file look like.
It will be just simpler to use. And we can provide templates which will exhaust all
usual use-cases.
Michal Maczka
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWAR-2&page=comments#action_16710
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWAR-2
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPWAR-2
Summary: Include dependency as manifest-classpath
Type: Improvement
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-war-plugin
Assignee:
Reporter: Anders Engstr?m
Created: Sat, 20 Sep 2003 5:52 AM
Updated: Thu, 12 Feb 2004 6:18 AM
Description:
One nice feature for the war plugin would be to make it
possible to specify that a dependency should be included in the manifest classpath of
the war. Is is this something that is considered?
The jelly-code is in the ejb-plugin, so I suppose it would be pretty
easy to implement (I'd be happy to write a patch).
The reason is that when you have an ejb module and one or many
web-modules in a J2EE-project (as we have) you often have common
dependencies between these modules. Let's say you need commons-logging
in all modules then you'd probably want to include
commons-logging-x.x.x.jar in the EAR-file, and reference it from all
other modules as manifest classpath entries.
In the project.xml of a webapplication you would thus have:
<!-- This is a dependency shared by many modules -->
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</groupId>
<version>1.0.3</version>
<properties>
<war.manifest.classpath>true</war.manifest.classpath>
</properties>
</dependency>
<!-- This is a webapp dependency only -->
<dependency>
<groupId>webwork</groupId>
<artifactId>webwork</artifactId>
<version>1.3</version>
<properties>
<war.bundle>true</war.bundle>
</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]
