Issues with Upgrading Spring version due to osgi-extenderhttps://www.eclipse.org/forums/index.php/mv/msg/305586/815761/#msg_815761
Our Project relies on spring and the osgi-extender(org.eclipse.gemini.blueprint).

We were using Spring version 3.0.3.RELEASE and wanted to move to 3.1.0 RELEASE.
After consulting the spring forums(wasnt able to post the link):

Google for "springsource upgrade 3.1.0 from 3.0.3". The first result is the relevant one.

I was successful in ensuring that gemini-blueprint 1.0.0.M1 which has a reference to
SPRING 3.0.3 hardcoded in its pom, was prevented from pulling in 3.0.0 after we had pulled in the newer 3.1.0 jars for SPRING.

Now still our product has difficulty starting which points to gemini-blueprint complaining:

Now based on what I saw in the gemini-blueprint jar manifest it should be compatible with any spring version between 3.00 and 4.00. Is this not the case?
Is gemini-blueprint tightly coupled with the spring version.
For instance the 1.0.0.RELEASE jar pulls in the Spring version 3.0.6 on maven clean install. Is is there any way to get around this, ie using eclipse-gemini blueprint 1.0.0.M1 with spring 3.1.0.RELEASE. Thank you for your time.

]]>Zaraki r2012-03-08T02:20:15-00:00Re: Issues with Upgrading Spring version due to osgi-extenderhttps://www.eclipse.org/forums/index.php/mv/msg/305586/815966/#msg_815966
You may be interested to know that I am looking into replacing Spring DM 1.2.1 by Gemini Blueprint in Virgo which will move up to Spring 3.1.x before very long, so I may hit the same problem as you in due course.]]>Glyn Normington2012-03-08T09:14:06-00:00Re: Issues with Upgrading Spring version due to osgi-extenderhttps://www.eclipse.org/forums/index.php/mv/msg/305586/815973/#msg_815973
Glyn Normington2012-03-08T09:19:46-00:00Re: Issues with Upgrading Spring version due to osgi-extenderhttps://www.eclipse.org/forums/index.php/mv/msg/305586/821853/#msg_821853
The problem is at least from what I remember that Spring 3.1 introduced an api incompatibility with 3.1 by removing a constant (NULL) from the conversion service. The change in gemini blueprint should be trivial but I don't know why that field was dropped or how it should be replaced. This is in my experience the first time in that an upgrade of spring core caused an api problem. I would like to upgrade our osgi stack to spring 3.1 as well but didn't have time to investigate further...]]>Magnus Jungsbluth2012-03-15T22:25:37-00:00Re: Issues with Upgrading Spring version due to osgi-extenderhttps://www.eclipse.org/forums/index.php/mv/msg/305586/821862/#msg_821862
Magnus Jungsbluth2012-03-15T22:47:05-00:00