[
https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538974
]
Stuart McCulloch commented on FELIX-396:
----------------------------------------
Hi Eugene - I'll need a Maven POM that recreates the exact issue you see before
I can investigate further - otherwise there's no way to tell if the warnings
you see are valid (for example if your POM includes the same class via
Private-Package and Include-Resource) or not.
Also can you tell me which Maven artifact you were embedding when you saw
multiple versions of the same jar file in the final bundle?
> split-package warnings during embedding of transitive dependencies
> ------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> 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 bundle.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
