Description of problem: Stock tomcat6 packages provide the extras required to run tomcat6 with log4j. tomcat6-lib-6.0.24-78.el6_5.noarch : Libraries needed to run the Tomcat Web container Repo : main-updates Matched from: Filename : /usr/share/java/tomcat6/extras/tomcat-juli.jar Filename : /usr/share/java/tomcat6/tomcat-juli.jar Filename : /usr/share/java/tomcat6/extras/tomcat-juli-adapters.jar These extras are not packages in the tomcat 7 packages in EPEL. This means that the package can not reliably be used with log4j, as the extras have to be downloaded manually, and will have to be manually upgraded on each subsequent minor release update from EPEL. Ideally the tomcat package should reflect the tomcat6 package and include the extras required to function with log4j (the full tomcat-juli.jar and tomcat-juli-adapters.jar) Version-Release number of selected component (if applicable): tomcat7-7.0.33 How reproducible: Always Steps to Reproduce: 1. Run: repoquery -l tomcat6-lib 2. Run: repoquery -l tomcat-lib 3. Compare output - the tomcat-lib package is missing extras/tomcat-juli.jar and extras/tomcat-juli-adapters.jar Actual results: The tomcat-lib package is missing extras/tomcat-juli.jar and extras/tomcat-juli-adapters.jar Expected results: The tomcat-lib package contains extras/tomcat-juli.jar and extras/tomcat-juli-adapters.jar Additional info: N/A
https://github.com/csutherl/fedora-tomcat/commit/632f1f9 To configure log4j in the service wrapper; update LOGGING_PROPERTIES in tomcat.conf to point to the lib/log4j.properties config file and then follow https://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j. The configuration must be in lib, or on the classpath to get loaded.
Note: the tomcat-juli.jar and tomcat-juli-adapters.jar files came from the 7.0.65 distribution of tomcat. If the rebase doesn't pass QA, then these jars may need to change.
We cannot include binaries as Sources. Also we cannot build it as they just rebranding commons packages: see https://bugzilla.redhat.com/show_bug.cgi?id=1236297
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Moving it back to NEW per comment #3.
Closing per c#3.