Fix icu4j

[Pantelis Koukousoulas]

This is a dependency. We need to look at the corresponding fedora
package and the eclipse orbit package, upgrade/downgrade to the right
version, add missing files (in a subpackage?) like:

    * feature.xml
    * OSGified Manifest.MF
    * etc

Make sure that eclipse still builds and works with this package
symlinked instead of what the eclipse zip carries and push the
updated package to debian.

In short, for each dependency we might need:

    * updated source package
    * patch to the eclipse package to add the dependency and
      change the build scripts to use it
    * Testing
    * Upload to debian (talk to Andreas Tille about this part)

[Pantelis Koukousoulas (pktoss)]

Don't forget to look at http://fedoraproject.org/wiki/Features/Eclipse34
for the details

[Rockwalrus (rockwalrus)]

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.