Łukasz Dywicki created MNG-7072:
-----------------------------------
Summary: Ambiguity in handling of primary build artifact with
classifier
Key: MNG-7072
URL: https://issues.apache.org/jira/browse/MNG-7072
Project: Maven
Issue Type: Bug
Components: core
Affects Versions: 3.6.3
Reporter: Łukasz Dywicki
A request for clarification and definitive resolution for edge case found in
MGPG-75.
Currently {{MavenProject.setArtifact}} accepts an artifact with classifier. It
works in most of the cases and most of plugins I saw so far, but it does not
work with GPG plugin which looses primary artifact classifier and attaches
signature *without* classifier.
Most of the time this goes under radar since install plugin report no issues
and handles that properly. For release I was confirming we ended up with
missing gpg signatures.
End result of build is following:
* opensmarthouse-core-0.9.0-connectorio-1-*features.xml*
* opensmarthouse-core-0.9.0-connectorio-1.*xml.asc*
* opensmarthouse-core-0.9.0-connectorio-1-features.xml.md5
* opensmarthouse-core-0.9.0-connectorio-1-features.xml.sha1
First file is primary build artifact (using Karaf features packaging).
Reason for creating this issue is simple - either behavior outlined by
[~rfscholte] should be enforced (refuse of classifiers for primary artifact) or
GPG plugin and should be fixed. Given that Robert mentioned that it is
something related to core please treat this as an input for starting discussion
on how to handle this particular case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
