Gemini Blueprint Spring 4 support [message #1237764] |
Thu, 30 January 2014 14:25  |
Eclipse User |
|
|
|
Hi all
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?
regards
Reto
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1237771 is a reply to message #1237764] |
Thu, 30 January 2014 14:53   |
Eclipse User |
|
|
|
Hi,
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.
Regards,
Dmitry
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1407660 is a reply to message #1237771] |
Wed, 13 August 2014 06:37   |
Eclipse User |
|
|
|
Hi Dmitry
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.
Thanks
Marcos
Dmitry Sklyut wrote on Thu, 30 January 2014 09:53Hi,
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.
Regards,
Dmitry
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1411612 is a reply to message #1407660] |
Sat, 23 August 2014 22:14   |
Eclipse User |
|
|
|
Marcos,
Spring 4 is going to be the theme of BP 2.0.
I originally wanted to do a quick release base on spring 3.x but life got in the way.
There will be a 2.0 release in the next few month. Stay tuned for an announce.
Kind Regards,
Dmitry
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1456498 is a reply to message #1455044] |
Thu, 30 October 2014 12:30   |
Eclipse User |
|
|
|
Hello Marcos,
I will push the spring4 related changes today-tomorrow minus test-support. I will also set-up jenkins jobs to publish artifacts to nexus.
I am still working on test-support as spring 4 removed support for old Junit3 based test harness and it will take a bit more time to finish plus some more time to redo all of the integration tests.
core, io, mock, extender have been updated to use spring4.
Kind Regards,
Dmitry
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1470033 is a reply to message #1456498] |
Wed, 12 November 2014 03:23   |
Eclipse User |
|
|
|
Hi Dmitry
Thanks - any idea of when you can price a milestone release of this? I'm using the Eclipse Blueprint snapshot repo directly in our project for now, but obviously we can't release until we have a non-snapshot version, and I'd rather not release a fork.
Marcos
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1470988 is a reply to message #1470349] |
Wed, 12 November 2014 19:57   |
Eclipse User |
|
|
|
First good news: I made good progress on test-support. JUnit4 + PaxExam + Spring TestContext framework support. Still a lot of tests to move over but that is busy work mostly.
Now for not so good - servicemix bundles have an import range for commons-logging of [1.1.3, 2). slf4j has an export of 1.1.1. BAM.
I am in process of creating a patch to send to servicemix bundles. Once that gets accepted and they do a release, I will do a Milestone release.
If they do not accept it ... Lets just stay positive.
Hopefully a within a month we can have a 2.0 completed.
Dmitry
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1481385 is a reply to message #1470988] |
Fri, 21 November 2014 00:37   |
Eclipse User |
|
|
|
Hi Dmitry
Great news about version 2 coming along.
I hit upon the same issue with jcl-over-slf4j. What was your patch to the bundle? To revert to [1.1.1, 2) requirement?
I assume the reason is Spring itself bumped to 1.1.3: github.com/spring-projects/spring-framework/commit/8ae3aa7f59bea714abd7da681f487b5cf1b13165
An alternative I'm trying is to upgrade jcl-over-slf4j: github.com/qos-ch/slf4j/pull/89
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1482042 is a reply to message #1481385] |
Fri, 21 November 2014 12:38   |
Eclipse User |
|
|
|
Marcos, I am not so sure that changing slf4j version range is right solution. There is nothing in the commons-logging 1.1.2 and 1.1.3 that affects importers. No API change, only internal bug fixes. So I would argue that lowest boundary for import should still be 1.1.1 on spring side.
https://issues.apache.org/jira/browse/SMX4-1902
There was no movement on that issue so far. For now I will embed spring bundle generation into blueprint so I can push the changes to give interested parties something to test with. Once this gets resolved on either servicemix or slf4j side, I will update accordingly.
Kind Regards,
Dmitry
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1494736 is a reply to message #1470988] |
Mon, 01 December 2014 18:18   |
Eclipse User |
|
|
|
I'm trying out the blueprint 2.0.0.BUILD-SNAPSHOT code and get the following exception:
Root exception:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.springframework.core.SpringProperties.<clinit>(SpringProperties.java:50)
at org.springframework.beans.CachedIntrospectionResults.<clinit>(CachedIntrospectionResults.java:97)
at org.eclipse.gemini.blueprint.extender.internal.activator.JavaBeansCacheActivator.initJavaBeansCache(JavaBeansCacheActivator.java:62)
at org.eclipse.gemini.blueprint.extender.internal.activator.JavaBeansCacheActivator.start(JavaBeansCacheActivator.java:44)
at org.eclipse.gemini.blueprint.extender.internal.boot.ChainActivator.start(ChainActivator.java:93)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319)
at org.eclipse.osgi.container.Module.doStart(Module.java:571)
at org.eclipse.osgi.container.Module.start(Module.java:439)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory cannot be found by org.apache.servicemix.bundles.spring-core_4.1.1.RELEASE_2
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 21 more
I've include the commons-logging-1.2 bundle - this should satisfy spring-core_4.1.1 as it has a dependency of [1.1.3,2)
Any ideas how I can fix this?
|
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1514119 is a reply to message #1495828] |
Wed, 17 December 2014 03:44   |
Eclipse User |
|
|
|
Dmitry Sklyut wrote on Tue, 02 December 2014 09:54Servicemix bundles were updated with the correct version range.
I pushed new test-support changes, based on pax exam to master.
One step closer to 2.0 release.
Dmitry
Just checking in again to see if you have a timeline for the first rc? I'm assuming sometime after the holiday season at this stage?
|
|
|
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1689733 is a reply to message #1647221] |
Tue, 24 March 2015 07:53   |
Eclipse User |
|
|
|
HI Dmitry
We're chomping at the bit for a release of Blueprints 2.0.
We're faced with three options I think if this doesn't happen:
1) Revert to 1.x, but that would mean not being able to use Spring 4, and thus not really an option
2) Release an internal milestone with which to build and release our products against
3) Fork and make a public release
One other option we mooted was whether we could join the project? Is that something you'd consider? Do you have a list of outstanding work to do for a 2.0 version?
|
|
|
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1703758 is a reply to message #1237764] |
Tue, 04 August 2015 17:37   |
Eclipse User |
|
|
|
I've seen that you both were approved as committers to blueprint, congrats!
Is there a timeframe for merging the bitbucket branch?
Or maybe Marcus can make his mirror/fork public...
I would very much like to get my hands on it.
Jn
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1704995 is a reply to message #1704875] |
Tue, 11 August 2015 10:06   |
Eclipse User |
|
|
|
Florian Waibel wrote on Mon, 10 August 2015 06:15Hi,
as far as I know Marcos is currently busy with the required paperwork.
Regards,
florian
Yes that's correct Florian - I need to ensure the company I work with can sign the employer consent form.
Will update as soon as that happens.
[Updated on: Tue, 11 August 2015 10:11] by Moderator Report message to a moderator
|
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1708644 is a reply to message #1705277] |
Fri, 18 September 2015 10:30   |
Eclipse User |
|
|
|
I did find an issue where within the workspace Eclipse tries to use the Servicemix Spring SOURCE bundle jars instead of the binary jars as plug-in dependencies, when both are present on the target platform. I reported this here and commented on a related servicemix bug here.
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1709351 is a reply to message #1237764] |
Sun, 27 September 2015 11:08   |
Eclipse User |
|
|
|
Is someone actively working on gemini blueprint to get the 2.0.0 release including spring 4 support done and finally available to everyone?
If so, please give some sense of urgency to it.
If not, is there a way we can assist in it?
Tom
ACA IT SOLUTIONS
Belgium
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1709464 is a reply to message #1709351] |
Mon, 28 September 2015 15:56   |
Eclipse User |
|
|
|
Hi Tom
It's been quite a long process of getting voted as a committer, getting legal contributer agreements signed, and finally getting SSH access to the code I'm afraid.
However, the good news is I've finally done that, and hopefully now I can get the fixes I made to the tests committed.
The next hurdle is that Blueprints Gemini doesn't appear to be using Gerrit, so I need to check with Dmitry how he did code reviews before now.
[Updated on: Mon, 28 September 2015 15:57] by Moderator Report message to a moderator
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1712633 is a reply to message #1710002] |
Tue, 27 October 2015 04:33   |
Eclipse User |
|
|
|
I'm also interested in when there will be a new release.. In the meantime can we just release a snapshot to maven repo. Current snapshot is pointing to spring snapshot in servicemix that's not there. The code in github appears to point to correct location..
Thanks,
Garry
|
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1717989 is a reply to message #1237764] |
Fri, 18 December 2015 12:52   |
Eclipse User |
|
|
|
Thanks for the recent release with spring 4 support! Would it be possible to provide a release with spring 4.2+ support? It only requires a few (3) trivial changes, I've made them locally and can provide a patch if that helps.
|
|
|
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1728325 is a reply to message #1727547] |
Sat, 02 April 2016 00:46   |
Eclipse User |
|
|
|
What is the trick to building it? When I enter
mvn -e -P equinox clean compile
I get
[ERROR] Failed to execute goal org.eclipse.virgo.bundlor:org.eclipse.virgo.bundlor.maven:1.1.2.RELEASE:bundlor (bundlor) on project gemini-blueprint-mock: Execution bundlor of goal org.eclipse.virgo.bundlor:org.eclipse.virgo.bundlor.maven:1.1.2.RELEASE:bundlor failed: No value found for placeholder 'spring.maven.artifact.version' -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.virgo.bundlor:org.eclipse.virgo.bundlor.maven:1.1.2.RELEASE:bundlor (bundlor) on project gemini-blueprint-mock: Execution bundlor of goal org.eclipse.virgo.bundlor:org.eclipse.virgo.bundlor.maven:1.1.2.RELEASE:bundlor failed: No value found for placeholder 'spring.maven.artifact.version'
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution bundlor of goal org.eclipse.virgo.bundlor:org.eclipse.virgo.bundlor.maven:1.1.2.RELEASE:bundlor failed: No value found for placeholder 'spring.maven.artifact.version'
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.RuntimeException: No value found for placeholder 'spring.maven.artifact.version'
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolve(PropertyPlaceholderResolver.java:117)
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolve(PropertyPlaceholderResolver.java:129)
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolveProperty(PropertyPlaceholderResolver.java:109)
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolve(PropertyPlaceholderResolver.java:102)
at org.eclipse.virgo.bundlor.support.propertysubstitution.PlaceholderManifestAndTemplateModifier.modify(PlaceholderManifestAndTemplateModifier.java:50)
at org.eclipse.virgo.bundlor.support.StandardManifestGenerator.generate(StandardManifestGenerator.java:49)
at org.eclipse.virgo.bundlor.maven.plugin.internal.MavenBundlorExecutor.execute(MavenBundlorExecutor.java:68)
at org.eclipse.virgo.bundlor.maven.plugin.BundlorMojo.execute(BundlorMojo.java:222)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
|
|
|
Re: Gemini Blueprint Spring 4 support [message #1728467 is a reply to message #1728325] |
Mon, 04 April 2016 14:48   |
Eclipse User |
|
|
|
Russell, I get the same result building the master branch.
My settings:
$ mvn -v
Apache Maven 3.3.9
Java version: 1.8.0_77, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.16.0-67-generic", arch: "amd64", family: "unix"
You can set the value on the command line, i.e.
mvn -e -Dspring.maven.artifact.version=4.1.6.RELEASE_1 -P equinox clean compile
But then I get
java.lang.RuntimeException: No value found for placeholder 'git.commit.id.describe'
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolve(PropertyPlaceholderResolver.java:117)
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolve(PropertyPlaceholderResolver.java:129)
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolveProperty(PropertyPlaceholderResolver.java:109)
at org.eclipse.virgo.util.common.PropertyPlaceholderResolver.resolve(PropertyPlaceholderResolver.java:102)
at org.eclipse.virgo.bundlor.support.propertysubstitution.PlaceholderManifestAndTemplateModifier.modify(PlaceholderManifestAndTemplateModifier.java:50)
at org.eclipse.virgo.bundlor.support.StandardManifestGenerator.generate(StandardManifestGenerator.java:49)
at org.eclipse.virgo.bundlor.maven.plugin.internal.MavenBundlorExecutor.execute(MavenBundlorExecutor.java:68)
at org.eclipse.virgo.bundlor.maven.plugin.BundlorMojo.execute(BundlorMojo.java:222)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Anyway it should not be necessary to declare on the command line because it is set in the parent POM.
|
|
|
|
|
|
|