Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Message-ID: <32373082.1174876352158.JavaMail.jira@brutus>
Date: Sun, 25 Mar 2007 19:32:32 -0700 (PDT)
From: "Stuart McCulloch (JIRA)" <jira@apache.org>
To: felix-dev@incubator.apache.org
Subject: [jira] Commented: (FELIX-255) maven-bundle-plugin, wrapping and
 excludeTransitive
In-Reply-To: <9875853.1173804429228.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484005 ] 

Stuart McCulloch commented on FELIX-255:
----------------------------------------

I think we have to be careful not to spend too much time trying to fix the issues of transitive dependencies in Maven when this is likely to be resolved in the future outside of the plugin. At the moment the only way to use the normal dependency list and not drag along all the transitive dependencies is to use the 'provided' scope - unfortunately this means the artifacts don't appear on the project artifact list in the bundle plugin.

So the question really is: can we get these 'provided' dependencies in a way that doesn't break the maven model, and how complicated is it?

In the meantime, there is a workable solution which people can use while this issue is properly investigated.

> 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.