[
https://issues.apache.org/jira/browse/MJAR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957200#comment-17957200
]
Matthias Bünger commented on MJAR-130:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#160|https://github.com/apache/maven-jar-plugin/issues/160].
> Sign goal fails on projects with maven-plugin packaging
> -------------------------------------------------------
>
> Key: MJAR-130
> URL: https://issues.apache.org/jira/browse/MJAR-130
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Edd Steel
> Priority: Major
>
> If you run jar:sign on a project with maven-plugin packaging, jarsigner is
> run with the argument '<build dir>/<projectname>-<version>.maven-plugin'
> instead of '<build dir>/<projectname>-<version>.jar'.
> A workaround is to add the configuration:
>
> <jarPath>${project.build.directory}/${project.build.finalName}.jar</jarPath>
> which is not very elegant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
