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 2015/03/09 21:26:38 UTC

[jira] [Resolved] (SM-2470) Wrong version range for joda-time in spring-context bundle

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

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

> Wrong version range for joda-time in spring-context bundle
> ----------------------------------------------------------
>
>                 Key: SM-2470
>                 URL: https://issues.apache.org/jira/browse/SM-2470
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: bundles
>            Reporter: Krzysztof Sobkowiak
>            Assignee: Jean-Baptiste Onofré
>             Fix For: bundles-2015.02
>
>
> All versions of the spring-context bundle define following import rules for joda-time dependency
> {code}
> org.joda.time;version="[1.6.0,2)";resolution:=optional,
> org.joda.time.format;version="[1.6.0,2)";resolution:=optional,
> {code}
> Spring uses Joda Time 2.x (e.g. 3.2.7: https://github.com/spring-projects/spring-framework/blob/v3.2.7.RELEASE/build.gradle#L331). 
> Due to the wrong range Spring resolves always Joda Time 1.6.2, but most of ther bundles which use Joda Time resolve the version 2.x. This causes unnecessary installation of Joda Time 1.6.2 and problems with bundle resolution (e.g. activiti)
> I propose to use [1.6.0,3) as a version range.



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