You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Eugene Kuleshov (JIRA)" <ji...@apache.org> on 2007/10/18 06:39:50 UTC
[jira] Created: (FELIX-396) Plugin should allow to specify
-split-package directive
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
Priority: Blocker
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.
Re: [jira] Commented: (FELIX-396) Plugin should allow to specify -split-package directive
Posted by Stuart McCulloch <st...@jayway.net>.
On 18/10/2007, Peter Kriens <Pe...@aqute.biz> wrote:
>
> 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.
yep - so the current question is whether the multiple package instances with
differing content
when using Embed-Transitive:* is due to a bug in the maven-bundle-plugin
wrt. dependencies,
or a problem with other instructions in the POM, or because there really are
non-duplicated jars
containing packages with different content...
all will (hopefully) become clear once Eugene provides his example POM :)
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
>
>
--
Cheers, Stuart
Re: [jira] Commented: (FELIX-396) Plugin should allow to specify -split-package directive
Posted by Peter Kriens <Pe...@aQute.biz>.
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
[jira] Updated: (FELIX-396) split-package warnings during embedding
of transitive dependencies
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-396:
-----------------------------------
Summary: split-package warnings during embedding of transitive dependencies (was: Plugin should allow to specify -split-package directive)
Fixed title to match problem text - note that it is possible to add the split-package directive in the BND instructions:
Export-Package: foo.bar;-split-package:=merge-first
you would need to explicitly do this when you are combining classes with the same package from different locations.
> 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
>
> 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.
[jira] Commented: (FELIX-396) Plugin should allow to specify
-split-package directive
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-396) Plugin should allow to specify
-split-package directive
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535830 ]
Stuart McCulloch commented on FELIX-396:
----------------------------------------
the bundle plugin does use Maven's dependency resolution mechanism - could you attach an example POM that shows this warning?
> 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
> Priority: Blocker
>
> 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.
[jira] Commented: (FELIX-396) Plugin should allow to specify
-split-package directive
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535846 ]
Stuart McCulloch commented on FELIX-396:
----------------------------------------
Hi Eugene, I will need an example POM to debug this issue as I have not been able to recreate this locally.
> 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
>
> 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.
[jira] Closed: (FELIX-396) split-package warnings during embedding
of transitive dependencies
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch closed FELIX-396.
----------------------------------
Resolution: Cannot Reproduce
Update from Eugene:
"... after your suggestions on FELIX-395, I can't reproduce issue from FELIX-396 anymore. So, I can't
make test project for you, but will keep an eye on that and if it happen again I'll update JIRA issue."
hence closing this issue as "Cannot Reproduce" - Eugene will reopen this if the problem reoccurs.
> 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.
[jira] Updated: (FELIX-396) Plugin should allow to specify
-split-package directive
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-396:
-----------------------------------
Priority: Major (was: Blocker)
This is not a blocking issue - the split package messages are only warnings.
> 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
>
> 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.
[jira] Updated: (FELIX-396) split-package warnings during embedding
of transitive dependencies
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-396:
-----------------------------------
Priority: Minor (was: Major)
Hi Eugene - could you supply a Maven POM that recreates this issue?
> 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.
[jira] Assigned: (FELIX-396) Plugin should allow to specify
-split-package directive
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-396:
--------------------------------------
Assignee: Stuart McCulloch
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-396) split-package warnings during
embedding of transitive dependencies
Posted by "Peter Kriens (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539852 ]
Peter Kriens commented on FELIX-396:
------------------------------------
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.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
> 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.
[jira] Commented: (FELIX-396) split-package warnings during
embedding of transitive dependencies
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ 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.