Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPJAR-41

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPJAR-41
    Summary: Allow jar plugin to update manifest file with dependency path if 
deployed in other directory
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: 30 minutes
 Time Spent: Unknown
  Remaining: 30 minutes

    Project: maven-jar-plugin
   Fix Fors:
             1.7

   Assignee: 
   Reporter: Eric Giguere

    Created: Wed, 15 Dec 2004 2:40 PM
    Updated: Wed, 15 Dec 2004 2:40 PM
Environment: Any

Description:
When deploying an application as a jar, we usually bundle dependencies with it. 
The current maven-jar plugin implementation allows that (using the 
jar.manifest.classpath) but it also implies that the dependency jar will be 
deployed with the produced jar.

Using the new introduced property : jar.dependency.dist.dir, we can add a sub 
distribution path to a dependency. Since most of the time all dependencies (or 
most) will be deployed in the same location, the property 
jar.dependency.dist.dir can also be declared at the project level and so, 
entries at dependency level would act as an override to project default 
dependency deployment location.

Ex. at project level:

<project>
...
    <properties>
        <jar.dependency.dist.dir>lib</jar.dependency.dist.dir>
    </properties>
...
</project>

Ex. at dependency level:
<dependency>
    <groupId>commons-logging</groupId>
    <artifactId>commons-logging</artifactId>
    <version>1.0.3</version>
    <url>http://jakarta.apache.org/commons/logging.html</url>
    <properties>
        <jar.manifest.classpath>true</jar.manifest.classpath>
        <jar.dependency.dist.dir>lib</jar.dependency.dist.dir>
    </properties>
</dependency>
 
Will add up shortly with the issue, the diff files (made against 1.6.1) for:
plugin.jelly

No other files are to be modified since currently, no documentation is supplied 
even for the jar.manifest.classpath property (should though... an issue is open 
for this).

But this said, I volunteer to correct the doc issues and include new 
documentation for this feature, if it is accepted.



---------------------------------------------------------------------
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]

Reply via email to