You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2021/01/16 06:06:00 UTC

[jira] [Assigned] (KARAF-6997) Regression in GenerateFeaturesMojo - primary artifact with classifier

     [ https://issues.apache.org/jira/browse/KARAF-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré reassigned KARAF-6997:
-------------------------------------------

    Assignee: Jean-Baptiste Onofré

> Regression in GenerateFeaturesMojo - primary artifact with classifier
> ---------------------------------------------------------------------
>
>                 Key: KARAF-6997
>                 URL: https://issues.apache.org/jira/browse/KARAF-6997
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.2.9
>            Reporter: Łukasz Dywicki
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>
> Refactoring in KARAF-5939 which was intended to support maven-install-plugin 3.0 M1 introduced an edge condition described in MNG-7072.
> The primary build artifact should not use classifier. Not sure why but generate features mojo assumes that *it is* making a primary artifact without chances to specify attach flag (as it is for achive mojo).
> The ultimate result is that releases which try to use generate features mojo + maven gpg plugin fail to pass signature verification. While it can be work-arounded with POM packaging (same way is used in Karaf to make spring features). Still we should stick with Maven core principles to minimize interferences in future releases of Maven.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)