karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-5986) Add support for exclusions based on both groupId/artifactId
Date Fri, 08 Mar 2019 13:46:00 GMT

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

Jean-Baptiste Onofré updated KARAF-5986:
----------------------------------------
    Fix Version/s:     (was: 4.2.4)
                   4.2.5

> 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.3.0, 4.2.5
>
>
> 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)

Mime
View raw message