This is almost trivial (just delete this line from the solr build.xml):
What that line is doing is overriding the top level target that does the checking and makes it do nothing.
BUT.... unfortunately the "almost" of this is that that instantly detects a large number of things, many of which are valid usages because they are in command line tools that really do want to report information to system out (I'll attach the output)
This leaves us with two possibilities:
- Add @ SuppressForbidden (though there seem to be two of these)
- Convert the CLI oriented code to use logging (probably a custom logging config for this use case with no leading date stamp etc...)
In the first case there's the additional question of whether or not we can suppress just the one bundle (jdk-system-out) or if we have to suppress all forbidden apis checks (which is a worrisome thought).
Also it's worth noting that a there are a couple of other detections relating to eclipse generated try/catch blocks that are triggered by removing the above line from the build.
Conversation on Slack indicates that [~thetaphi] will likely have some thoughts on this.
|Remove org.apache.solr.internal.csv.writer.CSVWriter (and related classes)||Resolved||Unassigned|
|Stop swallowing exception for Canonical URL in URLClassifyProocessor||Resolved||Unassigned|