InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

SpringSource Moves dm Server to Eclipse.org and EPL License with Project Virgo

Posted by Scott Delap on Jan 12, 2010

Sections
Development,
Operations & Infrastructure
Topics
Java ,
Application Servers
Tags
SpringSource dm Server ,
SpringSource ,
OSGi ,
Eclipse

This morning SpringSource announce the submission of the Virgo project at Eclipse.org. If accepted, this would result in the conversion of SpringSource's dm Server to the renamed Virgo project under <a href="http://eclipse.org/eclipsert/">EclipseRT</a>. It would then be fully licensed under the EPL (Eclipse Public License) in contrast to its current GPL form. From SpringSource's Adrian Colyer:

What does this mean for users of dm Server?

The move to Eclipse.org has a number of practical implications for users of dm Server:

  • Project hosting, home pages, forums, and downloads will all be moved to Eclipse.org infrastructure
  • The license will change from the current (largely) GPL license, to the Eclipse Public License (EPL)
  • It will be much easier for other organizations and community members to get involved in the ongoing development of Virgo

The combination of the license change and community hosting at Eclipse.org opens the codebase to a much broader set of users and developers.

The follow-on (2.1) release of dm Server will be developed and released from Eclipse.org.

Why is SpringSource making this change?

...There is a great deal of interest and innovation around enterprise OSGi and the dm Server. This interest is strongest amongst early adopters, and projects with requirements that match closely to the dynamically modular nature of the OSGi Service Platform. For a mainstream development team though, who just want to build an enterprise application as quickly as possible, and with as little hassle as possible, the costs currently associated with adopting enterprise OSGi can outweigh the short-term benefits. This situation needs to be addressed before enterprise OSGi can become the de-facto approach for mainstream enterprise application development...

The Eclipse Foundation's Executive Director Mike Milinkovich also applauds the move:

The past couple of years, “establish Eclipse runtime technology as the leading open source runtime platform” has been on the top of the list of the strategic goals of the Eclipse Foundation. The recently announced Gemini project — and now Virgo — go a long way towards realizing that vision.

InfoQ sat down with Adam Fitzgerald Director of Developer Relations at SpringSource to discuss the announcement further. Fitzgerald echoed Adrian's statements that the creation of the Virgo project is primarily driven by the desire to increase use of OSGi in the enterprise. SpringSource is happy to be assisting Eclipse in the possibly fulfillment of one of their 2010 goals of Eclipse runtime technology becoming a leading open source platform. He noted that lack of broad OSGi adoption and a fragmentation of implementations was hindering its growth. Hopefully Virgo will increase adoption and be more attractive to participation and contributions from other industry companies.

Fitzgerald also indicated that SpringSource would be contributing the tooling pieces of dm Server to the appropriate Eclipse projects such as WTP. In regards to the existing commercial users of dm Server he confirmed that SpringSource would continue to offer commercial support for what is becoming the Vertigo project. Finally InfoQ asked about Virgo direction going forward. Fitzgerald indicated that while SpringSource would be continuing to actively support development and provide advice on where it should head, those decisions would be left to the project. He noted that one possibly future enhancement the project might undertake would be pluggable web container support to allow the use of Eclipse's own Jetty in addition to the currently supported Tomcat.

Virgo is under the Eclipse Runtime (EclipseRT) project by Chris Aniszczyk Posted
  1. Back to top

    Virgo is under the Eclipse Runtime (EclipseRT) project

    by Chris Aniszczyk

    "If accepted, this would result in the conversion of SpringSource's dm Server to a top level Eclipse project that would be fully licensed under the EPL...


    This isn't correct, Virgo will exist under the Eclipse Runtime (EclipseRT) project at Eclipse.

    eclipse.org/eclipsert/

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.