https://bz.apache.org/bugzilla/show_bug.cgi?id=62945
--- Comment #3 from Remy Maucherat <r...@apache.org> --- (In reply to Andrei Costescu from comment #2) > It would be nice if the default config (that seems to be aware of > log4j-web*.jar already) would not - by default - assume that this jar has > also TLDs. That would require though that the global config needs to > allow/disallow jar scanning at a more granular level (so in this case > separate properties that apply only for TLD scanning). > > Could the default config be modified in that way? Current approach works but > I don't like the copy/paste needed to override jarsToScan with tldScan > (default jarsToScan could be changed I guess in future versions). Although > of course in the end the .war knows what is in it and can adjust these lists > to compensate for defaults. log4j-web isn't useful for TLDs, but contains other components which are scanned. Although it could be separate, both TLD and "other" scanning use the same default list, which means you can get the message for them. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
