Revision as of 13:03, 14 November 2013

Upgrade

The latest releases of Sonatype/Sisu are actually runtime wrappers that translate and delegate calls to their Eclipse/Sisu dependencies:

    <dependency>
      <groupId>org.sonatype.sisu</groupId>
      <artifactId>sisu-inject-bean</artifactId>
      <version>2.5.0</version>
    </dependency>

    <dependency>
      <groupId>org.sonatype.sisu</groupId>
      <artifactId>sisu-inject-plexus</artifactId>
      <version>2.5.0</version>
    </dependency>

This enables you to migrate gradually to the new API by mixing new components and libraries with those written against the old API.

Change imports

Once you have upgraded to Sonatype/Sisu 2.5.0 you can start migrating to the new API. In most cases this just involves changing imports:

All the old types have been marked as deprecated to help identify which components you need to upgrade.

Check bindings

After upgrading and changing imports the final step is to see if your application works as expected when you remove the Sonatype/Sisu artifacts and replace them with pure Eclipse/Sisu:

    <dependency>
      <groupId>org.eclipse.sisu</groupId>
      <artifactId>org.eclipse.sisu.inject</artifactId>
      <version>0.1.0</version>
    </dependency>

    <dependency>
      <groupId>org.eclipse.sisu</groupId>
      <artifactId>org.eclipse.sisu.plexus</artifactId>
      <version>0.1.0</version>
    </dependency>

If you find that some components are missing at runtime, it could be that you are relying on a library that still requires the old Sonatype/Sisu API. To confirm this turn on trace logging for Sisu; you can either use the sisu.debug system property to send Sisu trace logging to the console, or alternatively set the logging level for the 'Sisu' logger to trace. Any components that couldn't be loaded at runtime because of missing types will be logged under "Problem scanning...".