Hear! Hear!
Felix, I agree. This is a real warning, if you have it, then the same
packages on the class path multiple times with different content. This
is a source for extremely obscure and hard to debug errors.
Kind regards,
Peter Kriens
FMJ> [
FMJ>
https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535847
]
FMJ> Felix Meschberger commented on FELIX-396:
FMJ> -----------------------------------------
FMJ> In fact, this message is very valuable exactly because of the
FMJ> complex dependency tress that may exist from maven projects. This
FMJ> generally means that you have to be very carefull when defining
FMJ> your project possibly working with dependency exclusions to
FMJ> exactly decalre what you are expecting.
FMJ> And yes, there are many projects out there, which just pack too
FMJ> much dependencies and generate strange dependencies trees - one
FMJ> time I came over project which had a compile dependency on junit
FMJ> (and this project was not meant for testing :-) ).
FMJ> So I opt for not doing anything here - except perhaps enhancing
documentation on the wiki page.
>> 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 bundle.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
