felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuomas Kiviaho (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-954) Import-Package should include packages from optional Maven dependencies with resolution=optional
Date Tue, 27 Oct 2009 09:18:59 GMT

    [ https://issues.apache.org/jira/browse/FELIX-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770430#action_12770430

Tuomas Kiviaho commented on FELIX-954:

I was testing the 2.0.1 version of the plugin with 'bundleall' and came across this problem
as well. Not only did the plugin check every optional transitive dependency but also went
to check test scoped artifacts. With dom4j:dom4j:1.6.1 dependency bundling failed with stax:stax-ri:jar:1.0:test
which isn't available in central repo. 

I assume this will happen with optional packages as well and maven exclusions don't seem to
have any effect on the process.

* * *

[DEBUG] Will bundle the following dependency tree
   (dom4j:dom4j:jar:1.5.2:compile - omitted for cycle)

> Import-Package should include packages from optional Maven dependencies with resolution=optional
> ------------------------------------------------------------------------------------------------
>                 Key: FELIX-954
>                 URL: https://issues.apache.org/jira/browse/FELIX-954
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-1.4.3
>            Reporter: Pavol Juhos
>             Fix For: maven-bundle-plugin-2.1.0
> It would be great if maven-bundle-plugin used resolution=optional for packages that are
coming from _optional_ Maven dependencies.
> The current behavior causes problems e.g. when embedding libraries with lots of optional
dependencies. As described by Detelin Yordanov: "[I]t seems that BND finds the
> references to [the optional packages] and assumes them to be mandatory adding a bunch
of imports in the manifest." This can easily result in hundreds of import-package declarations
importing packages that are actually not required by the application. In these cases it is
not practical to handle this manually in the plug-in / BND configuration.
> This issue was already discussed on felix-users list in Jan 2009 -- see thread "Maven
bundle plugin: Is it possible to mark optional Maven dependencies to be imported with resolition=optional"
> http://mail-archives.apache.org/mod_mbox/felix-users/200901.mbox/%3C81f0d9c0901280604x6097dc19r8aa460673bfdad6@mail.gmail.com%3E

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message