[
https://issues.apache.org/jira/browse/FELIX-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483974
]
Alin Dreghiciu commented on FELIX-255:
--------------------------------------
I think this two can go hand-in-hand. If the dependency plugin is the solution
then also this will be solved. But as in FELIX-262 is too verbose. At least to
me...
> maven-bundle-plugin, wrapping and excludeTransitive
> ---------------------------------------------------
>
> Key: FELIX-255
> URL: https://issues.apache.org/jira/browse/FELIX-255
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Reporter: Alin Dreghiciu
>
> Posted also on the list at
> http://www.mail-archive.com/felix-dev@incubator.apache.org/msg04299.html.
> Most of the time (at least in the cases I had) you would like to wrap only
> the content of the jar you are targeting and not also the transitive
> dependencies that the targeted jar has. You can do this in at least two
> ways:
> 1. add <exclusions> to the dependency. This is verbose for the case that the
> targeted jar has extensive dependencies and irrelevant to the process of
> wrapping
> 2. set the Export-package directive to export only those packages that you
> want. here you have to know the internals of the package and if the jar has
> some resources as licences, xmls' outside the main package you have to add
> them one by one.
> So, here I am proposing a new configuration option: excludeTransitive that
> is suppose to exclude the transitive artifacts if set to true.
> An example implementation can be found at the following location:
> http://maven.apache.org/plugins/maven-dependency-plugin/xref/org/apache/maven/plugin/dependency/utils/filters/TransitivityFilter.html
> Alin Dreghiciu
> PS. Maven does not support a property of the articat as isTransitive()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
