summaryrefslogtreecommitdiff
path: root/test/command_callback/checkstyle_paths
diff options
context:
space:
mode:
authorHoracio Sanson <horacio@allm.net>2019-06-10 10:18:06 +0900
committerHoracio Sanson <horacio@allm.net>2019-06-12 10:53:28 +0900
commiteb6a7b75164ae2a0acb87fc9a7402779dc3e3614 (patch)
treecfffe37c9c9b04f8d4001cfa3b5d1a7fe49472cd /test/command_callback/checkstyle_paths
parent80ab12c7b645b392feb98723873d77b045a0a7e2 (diff)
downloadale-eb6a7b75164ae2a0acb87fc9a7402779dc3e3614.zip
Fix checkstyle default configuration.
Checkstyle xml configuration is mandatory and not providing one causes the tool to fail with the following error: Must specify a config XML file. Checkstyle itself contains a default configuration as part of its assests named `/google_checks.xml`. Invoking checkstyle with this config works even if such file does not exists in the file system: checkstyle -c /google_checks.xml This should be the default invocation to allow ALE to use checkstyle with zero configuration. Also when a user sets `g:ale_java_checkstyle_config` option, ALE should use it to invoke checkstyle even such file does not exists in the filesystem. This is because checkstyle is able to use configuration files within JAR files defined in the CLASSPATH. The default `/google_checks.xml` is an example of such configuration available within a JAR resource.
Diffstat (limited to 'test/command_callback/checkstyle_paths')
-rw-r--r--test/command_callback/checkstyle_paths/google_checks.xml0
1 files changed, 0 insertions, 0 deletions
diff --git a/test/command_callback/checkstyle_paths/google_checks.xml b/test/command_callback/checkstyle_paths/google_checks.xml
deleted file mode 100644
index e69de29b..00000000
--- a/test/command_callback/checkstyle_paths/google_checks.xml
+++ /dev/null