[jira] [Resolved] (SMX4-1746) Define better import package version range in Spring bundles

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

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

Jean-Baptiste Onofré resolved SMX4-1746.
----------------------------------------

    Resolution: Fixed

> Define better import package version range in Spring bundles
> ------------------------------------------------------------
>
>                 Key: SMX4-1746
>                 URL: https://issues.apache.org/jira/browse/SMX4-1746
>             Project: ServiceMix 4
>          Issue Type: Improvement
>          Components: Bundles
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: bundles-2014.05
>
>
> The Spring bundles currently define import for Spring packages like this:
> {code}
> org.springframework.core;version=3.2.8.RELEASE
> {code}
> which means in OSGi: [3.2.8.RELEASE,)
> Using a OSGi resolver (like the Felix one), it drives to not consistent wiring where Spring 3.2.8.RELEASE bundles may use Spring 4.0.2.RELEASE bundles for instance.
> To be more consistent, the Spring bundles should use a version range like this (for Spring packages):
> {code}
> org.springframework.core;version="[3.2.8.RELEASE,3.3)"
> {code}
> where 3.2.8.RELEASE is the current Spring version of the bundle.



--
This message was sent by Atlassian JIRA
(v6.2#6252)