Jump to: navigation, search

Virgo/Community/Migrating from 3.0.x to 3.5.0

< Virgo‎ | Community
Revision as of 11:05, 20 December 2011 by Gnormington.vmware.com (Talk | contribs) (Custom Logback Appenders)

Modified Directory Layout

Virgo's distributions will have a slightly modified directory layout from 3.5.0 onwards. It closely matches an Eclipse-like directory layout. This enables us to seamlessly provide p2 initial provisioning support to all Virgo distributions. The documentation will be thoroughly updated with all changes and the configuration impact on the server.

The main differences are:

  • relocated configuration folder(from /work/osgi/configuration to /configuration)
  • relocated lib/kernel folder(from /lib/kernel to /plugins)

This also brings changes to the OSGi configuration of the server previously found in lib/org.eclipse.virgo.kernel.launch.properties. It is now contained in the standard for Equinox config.ini file in the /configuration directory.

Transformer Signature

Transformer services in Virgo 3.5.0 operate in terms of a directed acyclic graph of install artefacts instead of the tree which was used by Virgo 3.0.x.

If you provide a Transformer service, you'll need to rework it to implement the modified signature. For example, the WebTransformer.transform method was changed as follows:

public void transform(GraphNode<InstallArtifact> installGraph, InstallEnvironment installEnvironment) throws DeploymentException {
 installGraph.visit(new ExceptionThrowingDirectedAcyclicGraphVisitor<InstallArtifact, DeploymentException>() {

     public boolean visit(GraphNode<InstallArtifact> node) throws DeploymentException {
             InstallArtifact installArtifact = node.getValue();

Custom Logback Appenders

This will apply once bug 362095 is implemented.

Fragments containing custom Logback appenders now need to specify:

Fragment-Host: com.springsource.ch.qos.logback.classic

instead of:

Fragment-Host: org.eclipse.virgo.medic.core