felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-396) Plugin should allow to specify -split-package directive
Date Thu, 18 Oct 2007 06:11:50 GMT

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

Felix Meschberger commented on FELIX-396:

In fact, this message is very valuable exactly because of the complex dependency tress that
may exist from maven projects. This generally means that you have to be very carefull when
defining your project possibly working with dependency exclusions to exactly decalre what
you are expecting.

And yes, there are many projects out there, which just pack too much dependencies and generate
strange dependencies trees - one time I came over project which had a compile dependency on
junit (and this project was not meant for testing :-) ).

So I opt for not doing anything here - except perhaps enhancing documentation on the wiki

> Plugin should allow to specify -split-package directive
> -------------------------------------------------------
>                 Key: FELIX-396
>                 URL: https://issues.apache.org/jira/browse/FELIX-396
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>            Reporter: Eugene Kuleshov
>            Assignee: Stuart McCulloch
> When using plugin with <Embed-Transitive>true</Embed-Transitive> and more
or less complex dependency tree it is really easy to receive the following warning:
> [WARNING] Warning building bundle org.foo:boo-bundle:bundle:0.0.1 : There are split packages,
use directive -split-package:=(merge-first|merge-last) on instruction to get rid of this warning:
META-INF, classpath: [Jar:., <skipped>] from: C:\repo\commons-io\commons-io\1.3.1\commons-io-1.3.1.jar
> Ideally plugin should take care of this by using Maven's dependency resolution mehanisms,
so there won't be any conflicting jars.
> Also note that when <Embed-Dependency>*;inline=false</Embed-Dependency> and
above warning happens, plugin also include multiple versions of the jar file into the result

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

View raw message