Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
Milestone 6 of Virgo Maya (3.0) introduces a new shell, makes available the snaps framework supporting modular OSGi web applications, increases compliance with certain OSGi specifications (this is a backward incompatible change from milestone 5 - see below), upgrades Gemini Web to 2.0.0.M02, and fixes several bugs.
The new shell, based on Apache Felix Gogo, is not yet documented in the User Guide. See the Gogo home page for some basic usage information. Shells are provided for both kernel and user region.
Access is via ssh or telnet. The simplest way to access the shell is via telnet to port 2501 or 2401 for user region or kernel, respectively.
Alternatively, you can ssh to port 2502 or 2402 for user region or kernel, respectively. The first time you use ssh to connect, specify the user "equinox" and password "equinox". You'll then be prompted prompted to create a new user, password, and role (the "admin" role is recommended).
The shell ports may be reconfigured by editing config/osgi.console.telnet.properties or config/osgi.console.ssh.properties for the kernel, or repository/ext/osgi.console.telnet.properties or repository/ext/osgi.console.ssh.properties for the user region, and then restarting Virgo.
The shell currently has a few known bugs.
Milestone 6 includes a backward Incompatible Change to the handling of Web Application Bundle (WAB) manifest headers.
This may affect any WAB. Note that a WAB is distinguished from a WAR file by the presence of one or more of the manifest headers: Bundle-SymbolicName, Bundle-Version, Bundle-ManifestVersion, Import-Package, or Web-ContextPath. So if milestone 6 affects the processing of a WAR file, the chances are the WAR is actually a WAB.
Prior to milestone 6, the following defaults are applied to WAB manifest headers:
As a migration aid, which may be removed in future releases, it is possible to re-instate the defaulting of WAB manifest headers by setting the following property value in config/org.eclipse.virgo.web.properties:
This is described in the User Guide section "Configuring the Web Integration Layer".
A full list of bug fixes included in this milestone is available here.
Back to the top