Do not set default binary.

The default binary "launcher" is too generic and can get mixed with
other tools. To use this linter user must explicitly set the absolute
path of the launcher path.
This commit is contained in:
Horacio Sanson 2019-06-09 14:02:50 +09:00
parent 5ce97f8cdb
commit e84c9b300b
2 changed files with 2 additions and 2 deletions

View File

@ -1,7 +1,7 @@
" Author: Horacio Sanson <https://github.com/hsanson> " Author: Horacio Sanson <https://github.com/hsanson>
" Description: Support for the Java language server https://github.com/georgewfraser/vscode-javac " Description: Support for the Java language server https://github.com/georgewfraser/vscode-javac
call ale#Set('java_javalsp_executable', 'launcher') call ale#Set('java_javalsp_executable', '')
function! ale_linters#java#javalsp#Executable(buffer) abort function! ale_linters#java#javalsp#Executable(buffer) abort
return ale#Var(a:buffer, 'java_javalsp_executable') return ale#Var(a:buffer, 'java_javalsp_executable')

View File

@ -6,7 +6,7 @@ After:
call ale#assert#TearDownLinterTest() call ale#assert#TearDownLinterTest()
Execute(The javalsp callback should return the correct default value): Execute(The javalsp callback should return the correct default value):
AssertLinter 'launcher', ale#Escape('launcher') AssertLinter '', ale#Escape('')
Execute(The javalsp java executable should be configurable): Execute(The javalsp java executable should be configurable):
let b:ale_java_javalsp_executable = '/bin/foobar' let b:ale_java_javalsp_executable = '/bin/foobar'