Project Plan For Sisu, version 0.1.0

Introduction

The Sisu project provides a dynamic dependency injection framework that can interact with OSGi services and Eclipse extensions.

The project is currently divided into two codebases:

• Sisu Inject -- Enhanced JSR330 container, builds on top of Google-Guice.
• Sisu Plexus -- Cleanroom Plexus container, builds on top of Sisu-Inject.

Release Deliverables

Sisu JARs will be made available in the Eclipse download area and published to the Maven Central Repository. The project also plans to provide a P2 update site using Eclipse/Tycho, but that is unlikely to happen until after the first couple of milestones.

Table of Contents

Release Milestones

Milestones will be published as committer time allows.

Table of Contents

Target Environments

Sisu consists of pure Java code and is expected to run on any JVM that supports Java SE 5 or newer.

Internationalization

None of the Sisu deliverables are internationalized, any log and exception messages use English.

Table of Contents

Compatibility with Previous Releases

Compatibility with Sonatype Sisu

API Contract Compatibility: To comply with Eclipse Foundation requirements, all Sisu Java types/packages will be moved into the org.eclipse.sisu namespace. An external compatibility layer is being considered for users of Sonatype Sisu.

Source Compatibility: To comply with Eclipse Foundation requirements, all Sisu Java types/packages will be moved into the org.eclipse.sisu namespace. While the API will undergo some refactoring and cleanup during the move to Eclipse, it is expected that only clients that use the Sisu extensions to JSR330 will need to update their imports and make minor code changes to successfully build against the new API.

Table of Contents

Themes and Priorities

Clean up API

The refactoring of code into the org.eclipse.sisu namespace provides an opportunity to remove deprecated code and clean up the API to ease future evolution and to improve usability.

Table of Contents

Appendix

Table of Contents