Support different configuration files for different modules based on the location of the configuration file

[nlou9]

How it works Now:
The checkstyle configuration files need to be passed with -c flag.

New Feature

In some scenarios, different modules require different configuration files. We need to create different checkstyle.xml files for different directories. It would be helpful if the tool could automatically find the nearest ancestor, like most other linting tools.

In our case, we use Bazel rules_lint with checkstyle tools. We need this workaround, as the tool does not handle it by itself.

[romani]

This repository is checkstyle library, not a final solution for anyone.

Due to history, this repository host Ant tasks to let users integrate to ANT build system.

CLI exists specifically for testing purposes and quick runs, or whatever you can do with it simple usage, not really was intended to be API.

You do integration to Bazel, ok, CLI is not enough for you, you should use our API to integrate as you want.

automatically find the nearest ancestor

This is very vague request, it means something special for your use case. It is ok, please implement this automatically find the nearest ancestor in your integration, as it makes sense only in Bazel or only in your extension.

In each folder you will apply your special logic to find checkstyle config, as you find it, run checkstyle on target folder or files with target config, save results in whatever place your extension expects.

Issue is closed.
Discussion can continue to help to use API