maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Gossé (JIRA) <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MJAR-118) Upgrade maven-archiver dependency to 2.4
Date Tue, 12 May 2009 13:33:44 GMT

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

Romain Gossé edited comment on MJAR-118 at 5/12/09 8:33 AM:
------------------------------------------------------------

I also need to set a more flexible classpath in the manifest, for example adding extra files
to the depency list gathered from the pom.

At least, the custom classpath feature is vital for me too.

I'll try bypassing the local pom of the plugin...

      was (Author: rgosse):
    I also need to set a more flexible classpath in the manifest, for example adding extra
files to the depency list gathered from the pom.

At least, the custom classpath feature is vital for me too.

Soren> how did you manage to do you workaround to make the plugin use archiver 2.4 ?
  
> 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

       

Mime
View raw message