[jira] [Commented] (MGPG-75) Creates a signature with the wrong name if a classifier is defined

2021-02-15 Thread Jira
[ https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284622#comment-17284622 ] Łukasz Dywicki commented on MGPG-75: Exact problem is when the primary project artifact specifies an

[jira] [Commented] (MGPG-75) Creates a signature with the wrong name if a classifier is defined

2021-02-14 Thread Mike Hummel (Jira)
[ https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284582#comment-17284582 ] Mike Hummel commented on MGPG-75: - Sorry for bother you: What exactly is the problem if a 'feature' is the

[jira] [Commented] (MGPG-75) Creates a signature with the wrong name if a classifier is defined

2021-01-15 Thread Jira
[ https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266252#comment-17266252 ] Łukasz Dywicki commented on MGPG-75: It is not. Not in case of custom packaging which Karaf made. In

[jira] [Commented] (MGPG-75) Creates a signature with the wrong name if a classifier is defined

2021-01-15 Thread Robert Scholte (Jira)
[ https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265816#comment-17265816 ] Robert Scholte commented on MGPG-75: In that case the pom itself is the main artifact and all other

[jira] [Commented] (MGPG-75) Creates a signature with the wrong name if a classifier is defined

2021-01-14 Thread Jira
[ https://issues.apache.org/jira/browse/MGPG-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17265565#comment-17265565 ] Łukasz Dywicki commented on MGPG-75: [~rfscholte] can you please refer place where constraint you talk