You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Krzysztof Sobkowiak (JIRA)" <ji...@apache.org> on 2015/06/08 23:16:00 UTC

[jira] [Assigned] (SM-2584) Use overrides.properties to override joda-time version

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

Krzysztof Sobkowiak reassigned SM-2584:
---------------------------------------

    Assignee: Krzysztof Sobkowiak

> Use overrides.properties to override joda-time version
> ------------------------------------------------------
>
>                 Key: SM-2584
>                 URL: https://issues.apache.org/jira/browse/SM-2584
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: assemblies
>            Reporter: Krzysztof Sobkowiak
>            Assignee: Krzysztof Sobkowiak
>             Fix For: 6.0.0
>
>
> SM-2469 is a sample of problem introduced by some features installing {{joda-time}} in differrent versions -- some standard features install the version 2.2 of joda-time bundle (and don't use the obr resolver) and bundles which depend on joda-time wire to this bundle. Later installation of activiti fails, because it needs higher version of joda-time (2.6) and activiti tries to resolve this bundle via multiple paths. 
> In SM-2469 we have configured the correct version of {{joda-time}} to be installed in early startup stage in {{startup.properties}}. It forces the bundle to be installed first and all other bundles wire to this version. It has solved the problem. But other features still install the version 2.2 of {{joda-time}}.
> We can use the {{override.properties}} file (KARAF-2752) to override all features installing {{joda-time}} with version from range {{[2,3)}} to install the correct version of this bundle 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)