It would appear there's no definitive logging in Tomcat of which jars were found to need or not need scanning for purposes of an optimal JarScanFilter configuration.
Could this be added? Either a "yes, I found stuff in this jar that justified it being scanned" or "no, I found nothing in this jar to justify it being scanned" logging would be really helpful IMHO. I find myself asking AI to try to discern such for larger library sets - or adding my own possibly errant attempts at such logging to Tomcat code. -- Jess Holle
