Fix tomcat5

[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 of the dependency to debian

For details of what Fedora needed to do to this package to get it
in shape, see
            http://fedoraproject.org/wiki/Features/Eclipse34
and follow the corresponding Bug #

[Rockwalrus (rockwalrus)]

AFAIK Eclipse doesn't depend on Tomcat as of 3.4. Instead it depends on jetty. The servlet dependency is satisfied in my ppa using the libservlet2.4-eclipse package.

[Ilya Barygin (randomaction)]

Eclipse 3.4 contains parts of Tomcat: Java Servlet API 2.4 (servlet-api.jar), JavaServer Pages API 2.0 (jsp-api.jar), and Jasper 2 (as org.apache.jasper), all from Tomcat 5.5.17.

[Rockwalrus (rockwalrus)]

servlet-api and jsp-api are already packaged in Debian as libservlet2.4-java, so they can be packaged using the Bundle-ClassPath trick.

I'll punt what to do about jasper right now, but it's strange that they use jasper from tomcat when jetty has it as well.

[Rockwalrus (rockwalrus)]

Oh, for an example of the Bundle-ClassPath script, see the libservlet-2.4-eclipse package in my ppa.

[Ilya Barygin (randomaction)]

Is it possible (and desirable) to include contents of libservlet-2.4-eclipse into the eclipse-full package, instead of having it as a dependency?

[Pantelis Koukousoulas (pktoss)]

Nah, I don't think so.

Instead, we now have a jar-removal branch where all remove-jar-blobs
work will be commited and we will just merge it all in one go.