[
https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266252#comment-17266252
]
Łukasz Dywicki commented on MGPG-75:
------------------------------------
It is not. Not in case of custom packaging which Karaf made. In case of
"features" packaging main artifact can be a XML file with features classifier.
I was asking about documentation for what you said about primary artifact
because existing api permit to set build artifact with classifier
({{MavenProject.setArtifact}}).
If its not permitted then core API should refuse such artifact straight a way.
A rule, even undocumented, without enforcement is not a rule. It is a bug. ;)
> 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)
