[
https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265565#comment-17265565
]
Łukasz Dywicki commented on MGPG-75:
------------------------------------
[~rfscholte] can you please refer place where constraint you talk about is
defined? The "it is not allowed that main artifacts have classifiers" seems
pretty limiting. Given that some builds might produce platform specific
artifacts (think of native builds) having classifiers for main artifacts
shouldn't be prohibited.
Its pretty sad that I was caught by this issue 19 months after PR solving it
was submitted.
> 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)
