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

Hi Robby,

1) jetty6-servlet-2.5-api should not Require anything else
2a) tomcat6-servlet-2.5-api should Provide servlet_2_5_api and not Require anything else.
2b) geronimo-specs packages should only Require what they really do, e.g. jsp_2_1_api should Require servlet_2_5_api
3a) I do agree in that apache-commons-logging might not Require any servlet_api
3b) I do agree in that apache-commons-logging might Require something like servlet_api >= 2.3

I hopefully will be able to look into it this weekend (just changing platform).

Additionally the community may want to further comment on this issue.

Cheers
Ralph

-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im Auftrag von Robby Morgan
Gesendet: Mittwoch, 4. Januar 2012 15:55
An: Discussion about JPackage project
Betreff: Re: [JPackage-discuss] Problem with apache-commons-logging dependency on servlet_2_5_api

Hi Ralph,

Thanks for your comment.  Here is my feedback:

1) I agree that jetty6-servlet-2.5-api should not Require jetty6, but I also don't want to satisfy a tomcat dependency with a jetty package.
2) tomcat6-servlet-2.5-api does not appear to satisfy the servlet_2_5_api dependency.  Also, if I choose geronimo-servlet-2.5-api, then it requires about 40 other Geronimo J2EE packages, so I'm in the same boat.
3) My point is that servlet_2_5_api is NOT a dependency of apache-commons-logging because any package that uses the portion of that library that is compiled against the Servlet API must already depend on some version of the Servlet API.  There are many applications that depend on apache-commons-logging, but don't have any dependency on the Servlet API.
3) If we insist on declaring a dependency, then I'd make the case that apache-commons-logging should depend on servlet_api, version 2.3 or higher.  That's at least what the Maven POM for the apache-commons-logging project declares.  If this were the case, then I could rightfully satisfy the dependency with any implementation of the Servlet 2.3, 2.4, 2.5 or 3.0 API.

Let me know what you think about this.  I'd love to address this in the proper way, but for now, it looks like I can use geronimo-servlet-2.5-api from the JPackage 5 repo to satisfy the dependency without any other unnecessary dependencies.

Thanks,
Robby

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Wednesday, January 04, 2012 5:28 AM
To: [email protected]
Subject: Re: [JPackage-discuss] Problem with apache-commons-logging dependency on servlet_2_5_api

Hi Robby,

there are in fact several packages providing servlet_2_5_api, in a sense of "this is a different, independent __coding__ of one and the same spec (i.e. PDF)".

1) IMHO jetty6-servlet-2.5-api should not Require jetty6 nor jetty6-core.
2) You could solve your problem by first installing the package of your choice providing servlet_2_5_api, e.g. from tomcat6 or from geronimo-specs.
3) You may be right in that should not Require servlet_2_5_api at runtime but instead declare it "somewhere" as an optional Requires. But where? And is servlet_2_5_api such a great catastrophe?

Again, IMHO, the key deficiency is (1).

Regards and many thanks for your contribution

Ralph

-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im Auftrag von Robby Morgan
Gesendet: Mittwoch, 4. Januar 2012 04:44
An: [email protected]
Betreff: Re: [JPackage-discuss] 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
_______________________________________________
JPackage-discuss mailing list
[email protected]
https://www.zarb.org/mailman/listinfo/jpackage-discuss
_______________________________________________
JPackage-discuss mailing list
[email protected]
https://www.zarb.org/mailman/listinfo/jpackage-discuss
_______________________________________________
JPackage-discuss mailing list
[email protected]
https://www.zarb.org/mailman/listinfo/jpackage-discuss