You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/01/16 00:00:00 UTC
[jira] [Updated] (MNG-7072) Ambiguity in handling of primary build
artifact with classifier
[ https://issues.apache.org/jira/browse/MNG-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MNG-7072:
--------------------------------
Description:
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 loses 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.
was:
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.
> 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
> Priority: Major
>
> 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 loses 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)