[jira] Updated: (MPJAR-41) Allow jar plugin to update manifest file with dependency path if deployed in other directory

["Lukas Theussl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MPJAR-41?page=all ]

Lukas Theussl updated MPJAR-41:
-------------------------------

    Fix Version:     (was: 1.8)

> Allow jar plugin to update manifest file with dependency path if deployed in other directory
> --------------------------------------------------------------------------------------------
>
>          Key: MPJAR-41
>          URL: http://jira.codehaus.org/browse/MPJAR-41
>      Project: maven-jar-plugin
>         Type: Improvement

>  Environment: Any
>     Reporter: Eric Giguere
>     Priority: Minor
>  Attachments: cvs-patch-plugin.jelly.txt
>
> Original Estimate: 30 minutes
>         Remaining: 30 minutes
>
> 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.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira