please see https://bz.apache.org/bugzilla/show_bug.cgi?id=63691#c10
If it's a designed feature, It should be targeted at tomcat 10, add a warning in upgrade guide.
I tried: jarsToSkip=* jarsToScan=somelistofjars I fail to see an issue, especially "As of 9.0.31, this now causes cascading startup failures.". Please accurately and fully describe the configuration and problems. We sometimes change undocumented behaviors that we consider to be broken. It is rare but it happens. Sometimes a flag is added to optionally restore them. First I need to understand the issue.
I think I could figure it out in the code. You did mean that jarsToSkip=* overrides whatever is set as jarsToScan I suppose. That's likely not what's intended since jarsToScan is documented as having higher priority than jarsToSkip. The wildcard will no longer set the ignore everything flag if jarsToScan is present. Not sure if that configuration makes that much sense overall though. The fix will be in 10.0.0-M4, 9.0.34, 8.5.54 and 7.0.104.
(In reply to Remy Maucherat from comment #3) > I think I could figure it out in the code. You did mean that jarsToSkip=* > overrides whatever is set as jarsToScan I suppose. That's likely not what's > intended since jarsToScan is documented as having higher priority than > jarsToSkip. The wildcard will no longer set the ignore everything flag if > jarsToScan is present. Not sure if that configuration makes that much sense > overall though. > The fix will be in 10.0.0-M4, 9.0.34, 8.5.54 and 7.0.104. You are right.