You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike Hummel (Jira)" <ji...@apache.org> on 2021/02/15 07:25:00 UTC
[jira] [Commented] (MGPG-75) Creates a signature with the wrong
name if a classifier is defined
[ https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284582#comment-17284582 ]
Mike Hummel commented on MGPG-75:
---------------------------------
Sorry for bother you:
What exactly is the problem if a 'feature' is the main artifact? It seems to be valide if the hole package is feature package that the main artifact IS the feature xml file. And maybe therefor the rule is NOT documented, because it's no a rule. (But I'm not in it to discuss in deep)
> Creates a signature with the wrong name if a classifier is defined
> ------------------------------------------------------------------
>
> Key: MGPG-75
> URL: https://issues.apache.org/jira/browse/MGPG-75
> Project: Maven GPG Plugin
> Issue Type: Bug
> Reporter: Mike Hummel
> Assignee: Robert Scholte
> Priority: Major
>
> See pull request [https://github.com/apache/maven-gpg-plugin/pull/2#event-2847163553]
>
> The main file of a feature project is a xml file and has a classifier. The plugin ignores the classifier and creates a signature with wrong name.
>
> The feature is created by the apache karaf maven plugin.
>
> The fix also use the classifier to create the correct signature file.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)