You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@servicemix.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2019/10/25 04:57:00 UTC

[jira] [Resolved] (SM-4176) servicemix bundle POI dependency tree includes original POI

     [ https://issues.apache.org/jira/browse/SM-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved SM-4176.
--------------------------------------
    Resolution: Fixed

> servicemix bundle POI dependency tree includes original POI
> -----------------------------------------------------------
>
>                 Key: SM-4176
>                 URL: https://issues.apache.org/jira/browse/SM-4176
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: bundles
>            Reporter: Christian Notenboom
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: bundles-2019.10
>
>
> We use servicemix bundle POI in our OSGi project which is build by maven. Sinds version 4.0.1_2 the maven configuration has introduced the folowing problem for us:
> mvn dependency:tree shows it depends on all org.apache.poi artifacts. This is not logical as it holds those artifacts itself and users of servicemix-bundle-poi shouldn't need that dependency. 
>  
> solution suggestion: make all dependencies on org.apache.poi optional = true (also the sources as those are already also included in the distributed jar). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)