|Gemini Blueprint Spring 4 support [message #1237764]
||Thu, 30 January 2014 09:25
| Reto Urfer
Registered: July 2009
Spring announced that after the current 3.2.7 release there will be only one
more bug fix release for Spring 3.2.
Currently Gemini Blueprint does not work with Spring 4 and is also not
compilable because in Spring 4 they have removed a lot of deprecated
classes. Spring 4 supports Java8 and also Hibernate 4.3 which contains the
JPA 2.1 implementation.
Therefore it is important to have a Spring 4 compatible version of Gemini
Blueprint. Are there any plans to migrate the current version so it will be
usable with Spring 4?
|Re: Gemini Blueprint Spring 4 support [message #1407660 is a reply to message #1237771]
||Wed, 13 August 2014 02:37
| Marcos Scriven
Registered: August 2014
I work on an application that uses Spring 3 and Gemini Blueprints. I just tried upgrading to Spring 4, and subsequently found this thread when things didn't work.
I just wanted to confirm a few things:
1) You mention that Spring 4 is not for a 2.x release, but I notice there's a relatively recent (9 days ago at the time of posting) tag in your git repo tagged 'spring4upgrade': http://git.eclipse.org/c/gemini.blueprint/org.eclipse.gemini.blueprint.git/log/?h=spring4upgrade
2) Regarding the Spring EBR releases, Servicemix publish these now. However, I see from the commit comment that that's what you used too.
3) When is Spring 4 support likely to land?
4) A more general question, but what's the roadmap? It looks like 2.0.0-m2 was released last year, and there's only been sporadic development work since (and only by you). Is Eclipse definitely supporting this?
Basically, wondering about the future of Spring in OSGi, and looking at whether we need to start preparing for pure Blueprint wiring.
Dmitry Sklyut wrote on Thu, 30 January 2014 09:53
Spring 4.0 support is a theme for post 2.x release. Maybe 3.x of blueprint. Current effort is to upgrade osgi frameworks support to OSGi R4.3 level (as felix does not have R5 certified release yet).
Another impediment is that Spring stopped shipping osgi metadata with official releases and Spring EBR is dead. Unless there is a desire on the part of Eclipse EBR project to wake up and start hosting maven/ivy repos of osgified artifacts we are all in a bit of a pickled situation.
Powered by FUDForum
. Page generated in 0.02207 seconds