commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Support for OSGi
Date Fri, 28 Dec 2007 12:35:55 GMT

in the meantime Stuart fixed the problem with the maven bundleplugin, so
I think we can give it a test drive :)

Attached is a patch for the parent pom of commons and one to demonstrate
how to add support for OSGi to commons-lang.

The changes to the parent pom are minimal: it just adds the maven
bundleplugin from the Apache Felix project. We currently need to use a
snapshot version, but a release is comming soon.
Besides adding the plugin, the patch also configures the bundle symbolic
name for all modules. The symbolic name is the unique identifier which
should follow java package naming. The best value is to use something
like "org.apache.commons.{artifactId}" where artifact id is commons-lang
or commons-collections etc.

The patch to commons lang is also very simple. It changes the parent pom
to the current snapshot (which includes the changes from above) and sets
the packaging to bundle - this ensures that the bundleplugin runs and
creates the resulting jar file. So the bundleplugin replaces the maven
jar plugin. If you leave the packaging as "jar" the bundleplugin will
not run.
The last part of the patch adds the configuration to the bundleplugin.
The export "*" exports all packages definied in this module for other
bundles, so all classes are public. All packages are marked with the
current version which allows to run different versions in parallel.
The imports are not specified as they are calculated automatically by
the bundleplugin.

And that's it :)

The changes to the other projects should be similar.


Carsten Ziegeler

View raw message