[
https://issues.apache.org/jira/browse/KARAF-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661709#comment-16661709
]
Jean-Baptiste Onofré commented on KARAF-5986:
---------------------------------------------
It sounds like a good idea to me. +1
> Add support for exclusions based on both groupId/artifactId
> ------------------------------------------------------------
>
> Key: KARAF-5986
> URL: https://issues.apache.org/jira/browse/KARAF-5986
> Project: Karaf
> Issue Type: Improvement
> Components: karaf
> Affects Versions: 4.2.1
> Reporter: Robert Varga
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.2.2
>
>
> Current mechanism for specifying artifact exclusion based on purely on
> artifactId is not sufficient to properly specify exclusions when artifact
> naming relies on groupId, too.
> One example is javax.activation:activation – here specifying to exclude
> "activation" may end up excluding other artifacts. This is needed to generate
> minimal features with JDK9+ and karaf: since jaxb and its dependencies are
> part of the boot class path, they should not end up being included in
> generated features.
> Add a more flexible scheme, which would handle groupIds, too, perhaps with
> the same syntax as maven-shade-plugin does here:
> https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#artifactSet
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
