First Virgo Milestone Ships |
|
The first milestone (2.1.0.M01) of Eclipse Virgo is now available for download under the Eclipse Public License. This consists of an application server, known as the Virgo Web Server, and a stand-alone kernel.
The goal of this milestone is for dm Server 2.0.x users to be able to migrate to it relatively painlessly and have an equally stable environment. SpringSource is offering commercial support for Virgo and we encourage all dm Server users to migrate to Virgo. The main communication channel with users is now the Virgo forum. There is also a Virgo developer mailing list and a weekly Virgo community call.
This is a major step for the Virgo project and demonstrates that the dm Server code contribution is complete. Users who want to package and distribute Virgo can now do so under the terms of the Eclipse Public License.
Documentation is available online in the form of a User Guide, a Programmer Guide, and a draft "getting started guide". Then there is a growing body of developer-oriented information — including a conceptual overview, a source code directory, and build tips — in the Virgo wiki.
Although the Eclipse-based dm Server application development tools will be contributed to Eclipse in due course, Virgo support has been added to the SpringSource Tool Suite in the interim. This is available by downloading STS 2.3.2 and installing the latest dm Server tools from the update site at http://www.springsource.com/snapshot/e3.5.
Background
In January Adrian Colyer announced our intention to donate SpringSource dm Server to Eclipse. The project proposal which was approved in February and the Virgo project created. Since then we have set up source code repositories, created a wiki, and tweaked the code in preparation for a formal release with full Eclipse legal approval. In May dm Server won the Eclipse Community Award for Best EclipseRT application, which is particularly fitting since Virgo is a subproject of EclipseRT.
Today's milestone demonstrates our continuing commitment to OSGi and to Virgo, the future of the dm Server project.
Similar Posts
- First Eclipse Gemini Web Milestone Ships
- Virgo milestone 4 ships
- First Eclipse Gemini Blueprint Milestone Ships
- dm Server project moves to Eclipse.org
- 5x startup performance boost in Virgo milestone M02
Chris Aniszczyk says:
Added on June 17th, 2010 at 7:45 amCongrats on the release guys!
I'm looking forward to the STS tools finding a nice home at Eclipse.
juan says:
Added on June 19th, 2010 at 6:59 amdoes this whole thing about virgo mean that springsource/vmware want to get rid of dm server and leave it only under development of eclipse community?
Glyn Normington says:
Added on June 19th, 2010 at 7:09 amHi Juan
Not at all. We have moved dm Server to Virgo for the reasons Adrian set out in his blog. SpringSource/VMware will continue to develop Virgo and provide commercial support.
Glyn
juan says:
Added on June 19th, 2010 at 1:35 pmPersonally I don't think Adrian gave an explanation on important questions such as amount of new development or bug fixes made by Springsource or if Springsource will keep "re-bundling" of 3rd party libraries to provide OSGi support. Article on Virgo plans/future would be also appreciated.
Glyn Normington says:
Added on June 21st, 2010 at 9:27 amHi Juan
We are exploring the possibility of moving the Enterprise Bundle Repository to Eclipse so that it becomes a community resource not dependent solely on SpringSource. I will be putting together a Virgo plan in due course, but for now I'm focussed on getting through the IP process. The most urgent functional enhancements are likely to be integrating with other EclipseRT components such as Jetty and p2. Meanwhile we are looking at important bug fixes and performance improvements.
Frieder says:
Added on August 8th, 2010 at 1:14 pmHi Glyn,
great news. Keep up the great work you all are doing with Virgo.
Anyway I have some questions for you regarding Virgo. I checked the bundles and it turned out that in the current milestone you're using the Equinox OSGI 3.5.1 bundle. I was wondering if there is any chance to replace the 3.5.1R35 bundles by the current 3.6 bundle and if so how to do that. I tried to just replace the OSGi bundle in the lib folder but then I got a lot of exceptions related to missing dependencies. Is there some tutorial available on which bundles need to be replaced to get this working? I'm asking because with 3.6 there is official support for AspectJ LTW. Currently I'm using plain Equinox 3.6 with AspectJ LTW but want to switch to Virgo because of improved support for web applications (e.g. GWT is a pain in the a.. with plain OSGi).
Moreover I was wondering why are you guys using the Felix bundles for the event admin, the config admin and the log stuff? Is there a specific reason why you didn't take the Equinox bundles?
Thx
Frieder
Glyn Normington says:
Added on August 20th, 2010 at 11:44 amThanks for your encouragement Frieder.
I raised bug 323270 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=323270) to cover upgrading to Equinox 3.6 as this is something we'd definitely like to see happen but haven't yet been able to squeeze into plan. Unfortunately, there's no tutorial available to show you how to do it. A contributor from SAP has however been working away at this and made good progress – see bug 322990 and the virgo-dev thread referenced by that bug.
As for the Felix services, when we did a code review of the Equinox equivalents back in the dm Server days, the code quality didn't look so good as Felix. However, we do plan to switch to the Equinox services now that Virgo is part of Eclipse RT. Any code issues which arise should be easier to get fixed if pain is being caused to another Eclipse project.
Regards,
Glyn