On Mar 29, 2013, at 12:57 PM, Konstantin Kolinko wrote: > 2013/3/29 Nick Williams <nicho...@nicholaswilliams.net>: >> >> >> (..) Note that Log4j2 is going to have a log4j-taglib artifact that >> (naturally) will have a TLD in its META-INF. Since Tomcat by default >> excludes log4j*.jar, that has to be removed from catalina.properties in >> order to make it work. It would be great for Tomcat 7/8 to ship with >> jarsToScan set to whitelist log4j-taglib*.jar, or (perhaps better) >> *taglib*.jar (which would cover any JARs that accidentally fell under the >> blacklist but had the word taglib in them). > > File an issue.
Done. 54770. > Do you have a link? I do not see such component at their web site, nor > I see it in download of apache-log4j-2.0-beta4-bin.zip https://issues.apache.org/jira/browse/LOG4J2-187 It's brand new and hasn't be committed yet. I wrote the component myself. As discussed in the Log4j developer list, it will get committed and be part of Log4j 2 at some point in the next week, hopefully. Desire is for it to be in -beta5. > > Possible solutions: > a) Use a more specific pattern instead of "log4j*.jar", e.g. the following > pair: > > log4j.jar,log4j-1*.jar, That's possible. I'd have to research whether that covers all Log4j 1 JARs. However... > > b) Remove this exclusion altogether. There might be not so many > classes in log4j to save much time, and it is not a library that > Tomcat itself uses. I wouldn't remove it altogether. There will be nine different log4j*.jar files, unless another component is added after mine, so not excluding the rest of the Log4j 2 JARs could result in needlessly scanning up to 8 extra JARs. Excluding all but log4j-taglib JAR would be best. > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org >
