Geek Answers Handbook

Should the new project use Spring DM 2.0.0.M1 or Gemni Blueprint 1.0.0.M1?

I am going to include Spring DM in a package that will run on the Apache Karaf OSGi framework. Given that Spring DM is migrating to Gemni Blueprint, should I use Spring DM 2.0.0.M1 or start with Gemni Blueprint 1.0.0.M1? Or should I go with the latest official release of Spring DM (1.2.1)? Any thoughts?

UPDATE:

This may be an argument against using Gemni Blueprint:

As of M1, not all modules or projects within Spring DM have been moved. At the moment, only io, core, extender and test modules switched presented in M1. Pending the release of OSGi RFC-66, website support is discontinuing. Existing users are invited to view the Eclipse Gemini web project. plans for the Maven archetype and undefined annotation extension for the moment. - http://www.eclipse.org/gemini/blueprint/documentation/migration/

The fact that not all Spring DM modules are included with Gemni Blueprint can make it difficult to run existing documentation. Has anyone tried to use Gemni Blueprint and Gemni Web to perform the same actions as with Spring DM?

+4
source share
1 answer

Since Spring DM was introduced to the Eclipse Foundation more than 1.5 years ago, I suggest you go with Gemini Blueprint:

At the end of 2009, Spring DM was added to the Eclipse Foundation as a Blueprint Gemini project. All new developments are now posted and released through the Eclipse Foundation. See the Gemini Blueprint website for details. For more information on the Gemini project and on the adoption of Spring DM, see the links below:

see here . The documentation for migrating from Spring DM is here .

You should also probably check out Virgo .

+3
source

More articles:


All Articles