...
- Document packages - Start documenting all our packages in all our projects with package-info.java files.
- Analyze dependencies - Refactor to improve coupling.
- Resolve obstacles - Track the status of obstacles to moving to OSGi to reduce the risk of making a bad container choice. See the "Obstacles" table, below.
Obstacle
Status
Move antlr wrapper from 'jconlon osgi-commons' to Felix.
Move commons-collections wrapper from 'jconlon osgi-commons' to Felix.
Move commons-lang wrapper from 'jconlon osgi-commons' to Felix.
Move jdbm wrapper from 'jconlon osgi-commons' to Felix.
Move jzlib wrapper from 'jconlon osgi-commons' to Felix.
Achieve Felix graduation.
Delete 'osgi' module from trunk.
Clean-up, doco, and enhancements to the protocols (Kerberos, etc.).
Achieve Felix 1.0 release with R4 support.
Non-snapshot Felix bundle plugin released and deployed to Ibiblio.
Bug fix in Maven when using multiple plugins.
Finish key enterprise features the server needs first.
Find/build an integration testing framework to easily test services within the target container as part of the maven build process.
Achieve good test coverage, testing the ApacheDS services inside an OSGi container (requires integration testing framework).
Solid documentation in Confluence for OSGi-based architecture for ApacheDS.
Greater team awareness of this OSGi based architecture.
Review OSGi alternatives like xbean.
Possibly wait for a Spring-OSGi release.
Time for us all to be involved to make sure something does not go wrong during this move to OSGi.
- Add OSGi metadata - Add the maven-bundle-plugin to our pom.xml files, one by one, to generate bundle jars with OSGi metadata.
- Use container - Switch 'server-main' to use Apache Felix, update installers, etc.
- Future enhancements - TBD, major functionality improvements taking full advantage of OSGi dynamics.
...