[
https://issues.apache.org/jira/browse/SLING-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196302#comment-13196302
]
Timo Naroska commented on SLING-2386:
-------------------------------------
I just stumbled into the exact same issue. The plugin already allows to specify
a <bundleExclusions> list in the pom.xml. Unfortunately the exclusions are not
considered for inherited partial bundle lists. i.e. AbstractUsingBundleListMojo
first loops through the exclusions and then merges inherited bundle lists.
IMHO the exclusions should be considered as last step after all merging is done.
> It should be possible to remove bundles from an inherited partial bundle list
> -----------------------------------------------------------------------------
>
> Key: SLING-2386
> URL: https://issues.apache.org/jira/browse/SLING-2386
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Maven Launchpad Plugin 2.1.2
>
>
> When a bundle list / launchpad project depends on a partial bundle list, it
> gets all the bundles from that list included.
> In some cases, it would be nice to exclude some of them to be able to replace
> them with a different implementation/bundle
> The easiest way would be to allow something like:
> <startLevel level="remove">
> <bundle>
> <groupId>commons-io</groupId>
> <artifactId>commons-io</artifactId>
> </bundle>
> </startLevel>
> in the bundle list. The version information is optional, If it is specified
> the bundle is only removed if it matches the given version or version range
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
