Eclipse Nano – a new streamlined future for Virgo?
Virgo nano distribution and move to p2 repository make it exciting times for Eclipse Virgo fans
It may have passed some by as it just about made the cut for New Year, but the newest milestone of Eclipse’s web server Virgo, 3.5.0 M1 brings forward some interesting features – p2 support and a new distribution known as Nano.
It shouldn’t be too difficult to work out what Nano is. Essentially, it’s a streamlined version of Virgo, complete with OSGi compliant Gemini Web, promising a rapid start-up time of 3 seconds (compared to the Virgo Tomcat/Jetty server’s 8-10 seconds) and a better runtime footprint. Nano has a single kernel region and is designed for simpler scenarios where you don’t need to isolate application from one another.
As well as introducing Nano, this milestone re-bases the Tomcat/Jetty servers on Nano. Another nifty use for Nano is automated or cloud deployments through dynamically provisioning content through p2.
As previously discussed in development of the Azure milestone (3.5.0 M1), the shift to p2 repository for all Eclipse services was expected. A p2 repository combines a metadata repository, used for resolution and an artifact repository, used for finding and collecting artifacts thus meaning that users depends upon not only the artifacts but programmes as well. This allows for flexibile targetting of the components that are needed, not the whole lot.
Through introducing Nano, the committers to Virgo has begun re-factoring the kernel and envisage the following set-up for the future
The release notes charter all the major changes for this release and also states what we can expect in M2 – further tooling support for Nano and the new directory layout, plus an improved Virgo Web Console. Plenty to be getting on with then – we look forward to the next milestone, hopefully enhancing Virgo that bit more.