[
https://issues.apache.org/jira/browse/MJAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957193#comment-17957193
]
Matthias Bünger commented on MJAR-118:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#158|https://github.com/apache/maven-jar-plugin/issues/158].
> Upgrade maven-archiver dependency to 2.4
> ----------------------------------------
>
> Key: MJAR-118
> URL: https://issues.apache.org/jira/browse/MJAR-118
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Sören Chittka
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: 2.3
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
