Re: Problem with apache-commons-logging dependency on servlet_2_5_api

Hi all,

I’m trying to upgrade to JPackage 6 from JPackage 5, so that I can get access to the latest Tomcat 6 (and ultimately Tomcat 7) packages, but I’m encountering an issue with JPackage6 that is forcing Jetty to be installed alongside Tomcat.  The dependency chain that appears to be causing this issue is thus:


1.       In JPackage6, tomcat6 depends on apache-commons-logging, which is a replacement package for jakarta-commons-logging (in JPackage 5).

2.       In JPackage6, apache-commons-logging declares a dependency on servlet_2_5_api.

3.       While tomcat6-servlet-2.5-api provides /usr/share/java/servlet_2_5_api.jar, it does not declare as such.

4.       Instead, yum sees that jetty6-servlet-2.5-api provides servlet_2_5_api and uses it to resolve the dependency.

5.       Also, jetty6 and jetty6-core are installed as dependencies of jetty6-servlet-2.5-api.

Long story short, I think there are a couple problems:

·         apache-commons-logging should not declare a dependency on servlet_2_5_api.  The Maven pom.xml declares a dependency on servlet-api:2.3, but that dependency is marked as “provided” because it is only necessary when using the ServletContextCleaner class in the context of a servlet container, and if the JAR is loaded in the context of a servlet container, then the dependency will have already been met.  Therefore, servlet_2_5_api is not a hard dependency of apache-commons-logging.

·         As long as the servlet_2_5_api logical dependency exists, then tomcat6-servlet-2.5-api should be designated as satisfying that dependency.  If this were the case, then I would not encounter issues with updating Tomcat6, although it wouldn’t help with Tomcat 7, which provides the servlet-api:3.0 JAR.

Can you please provide some input as to how best to address either of these two problems?  Thanks in advance for your help.

Thanks,
Robby