[jira] Updated: (MPWAR-2) Include dependency as manifest-classpath

[ji...@codehaus.org]

The following issue has been updated:

    Updater: Michal Szklanowski (mailto:michal.szklanowski@empolis.pl)
       Date: Thu, 12 Feb 2004 4:40 AM
    Comment:
This on was pretty easy to hack.
Assuming that used sets war.manifest.classpath property to true in dependency section, war:war goal geneated Class-Path entry of manifest based on these properties.

The change is implemented in attached file.

    Changes:
             Attachment changed to plugin.jelly
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWAR-2&page=history

---------------------------------------------------------------------
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 4:40 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org