Comment 2 for bug 309610

icu4j is kind of a special case in that the upstream project itself OSGifies the code instead of Orbit. You just call a different ant target with the icu4j code to create the OSGi version.

The OSGi build of icu4j is essentially identical to the stock build except that a few extra classes are added and the manifest obviously has a few changes. In other words, there is nothing that should cause compatibility issues if the OSGi jar is used for everything.

I have a version of icu4j in my ppa that updates the packaging to the 3.8.1 upstream version and switches it to use the target that builds the OSGi version.