You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2014/04/04 17:59:14 UTC
[jira] [Created] (SMX4-1746) Define better import package version
range in Spring bundles
Jean-Baptiste Onofré created SMX4-1746:
------------------------------------------
Summary: 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.04
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)