@leventov If there are compiled classes, forbidden-apis checks will work. That's the only reason. Taking the CI `strict compilation` as an example, the maven build command is `mvn clean -Pstrict -pl '!benchmarks' compile test-compile -B --fail-at-end`, `test-compile` is run after `compile`. So when maven run `test-compile` there are compiled classes for the forbidden-apis check plugin to work. But it just checks the source code classes not include test code classes because the test code compiled classes have not been generated(before this pr, the `testCheck` Mojo runs in the `validate` phase, if change to `test-compile` phase, test code classes would also be checked).
A CI build example [here](https://travis-ci.org/apache/incubator-druid/jobs/431840904), check the log then you'll figure it out. [ Full content available at: https://github.com/apache/incubator-druid/pull/6371 ] This message was relayed via gitbox.apache.org for [email protected]
