maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hardik Patel (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MJAR-119) Ugradation to support Maven Archiver 2.4
Date Thu, 11 Jun 2009 10:15:43 GMT

    [ http://jira.codehaus.org/browse/MJAR-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180012#action_180012
] 

Hardik Patel commented on MJAR-119:
-----------------------------------

I found the solution.

I was using following:
<customClasspathLayout>${artifact.artifactId}.${artifact.extension}</customClasspathLayout>

and thus was getting classpath entry in manifest as null.null.

Instead, the correct use if as follows:
<customClasspathLayout>$${artifact.artifactId}.$${artifact.extension}</customClasspathLayout>

Thanks, closing the improvement.

> Ugradation to support Maven Archiver 2.4
> ----------------------------------------
>
>                 Key: MJAR-119
>                 URL: http://jira.codehaus.org/browse/MJAR-119
>             Project: Maven 2.x Jar Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>         Environment: Windows XP
>            Reporter: Hardik Patel
>
> Maven Archiver 2.4 is out, Custom classpath entries are not possible in prior release
but, in Archiver 2.4 <customClasspathLayout> tag is supported. Is there any fix available
to use this tag for jar plugin? current 2.2 release is using Archiver 2.3.
> Can we have improvment version to support Archiver 2.4?

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

        

Mime
View raw message