[ 
https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284622#comment-17284622
 ] 

Łukasz Dywicki commented on MGPG-75:
------------------------------------

Exact problem is when the primary project artifact specifies an classifier. 
Then gpg mojo generates signature file but *without* classifier in its name. 
You end up with below files:
 * abcdef-1.0.0-SNAPSHOT-*features*.xml
 * abcdef-1.0.0-SNAPSHOT.asc

This is not critical, but when release is made it does not pass upload 
principles for maven central.

> 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)

Reply via email to