The command names "lint", "jshint" and "pylint" and hard-coded in the analyzer code, which means they must be installed and on the PATH. This isn't a problem when we use the container images, but androidlint_test fails locally if the Android SDK isn't on the PATH. (jshint and pylint would have the same problem, if they had tests. ;-).)
The paths to the analyzers should be configurable somehow, either via a flag or a local config file.
The command names "lint", "jshint" and "pylint" and hard-coded in the analyzer code, which means they must be installed and on the PATH. This isn't a problem when we use the container images, but androidlint_test fails locally if the Android SDK isn't on the PATH. (jshint and pylint would have the same problem, if they had tests. ;-).)
The paths to the analyzers should be configurable somehow, either via a flag or a local config file.