[jira] Commented: (MJAR-118) Upgrade maven-archiver dependency to 2.4

["Hardik Patel (JIRA)" <ji...@codehaus.org>]

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

Hardik Patel commented on MJAR-118:
-----------------------------------

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>



> Upgrade maven-archiver dependency to 2.4
> ----------------------------------------
>
>                 Key: MJAR-118
>                 URL: http://jira.codehaus.org/browse/MJAR-118
>             Project: Maven 2.x Jar Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Sören Chittka
>            Priority: Critical
>
> Hi,
> currently I am using the maven-jar-plugin 2.2.
> One of my project-teams really has the need to specify the <customClasspathLayout> introduced with maven-archiver 2.4.
> Just adding maven-archiver 2.4 to the dependencies of the maven-jar-plugin did not help.
> What I am trying is to use following <manifest>-entry in maven-jar-plugin:
> <manifest>
>   <addClasspath>true</addClasspath>
>   <classpathLayoutType>custom</classpathLayoutType>
>   <customClasspathLayout>${artifact.artifactId}.${artifact.extension}</customClasspathLayout>
> </manifest>
> But the classpath-entries are only resolved to null.null, I guess 'artifact' is not resolved to anything.

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