Update docs with new eclipselsp capabilities

Author: hsanson

README.md

@@ -24,12 +24,15 @@ If you are working in an Android project then set the *g:android_sdk_path*  with
 
 Open a java, kotlin or xml source file and this plugin will automatically kick in and perform some tasks:
 
- - Execute a custom vim gradle task to inspect the project and extract dependencies, project names, and android sdk versions.
- - Set CLASSPATH environment variable with the JAR dependencies of the project and the Android SDK jar.
+ - Execute a custom vim gradle task to inspect the project and extract
+   dependencies, project names, and android sdk versions.
+ - Set CLASSPATH environment variable with the JAR dependencies of the project
+   and the Android SDK jar.
  - Set SRCPATH environment variables with the project source sets.
  - Create Gradle and Android commands that can be used to invoke gradle tasks.
+ - Send didChangeConfiguration notification with Gradle and Android dependencies to `eclipselsp` (jdtls) or `javalsp` (java-language-server) if you have them configured with [ALE](https://github.com/dense-analysis/ale)
 
-Once the plugin finishes loading the Gradle command becomes available to use:
+Once the plugin finishes synchronizing gradle dependencies the Gradle command becomes available to use:
 
     :Gradle <task>
 
@@ -60,6 +63,10 @@ Combined with the ligthline plugin my status line looks like the following scree
  - Improved XML omnicompletion for android resource and manifest files. Thanks to [Donnie West](https://github.com/DonnieWest).
  - Customizable status line method that can be integrated with status line plugins (e.g. airline)
 
+## ALE
+
+In addition if you have [ALE](https://github.com/dense-analysis/ale) installed with either `eclipselsp` (recommended) or `javalsp` language servers, this plugin will send a [workspace/didChangeConfiguration](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_didChangeConfigurationmessage) notification to the language server with all gradle and Android dependencies. This enables ALE to auto-complete, auto-import, and go to definition of all dependencies, including Android core and generated classes (e.g. Activity, R, etc).
+
 # Details
 
 Refer to the [doc/vim-android.txt](doc/vim-android.txt) file for details on usage and configuration of this plugin.

doc/vim-android.txt

@@ -210,8 +210,8 @@ ANDROID OMNI-COMPLETION                              *vim-android-omnicomplete*
 
 This plugin by itself does not provide omni-completion of Android classes
 and/or methods. It is highly recommended to install ALE
-(https://github.com/w0rp/ale) with the `javalsp` LSP linter to get this
-functionality.
+(https://github.com/w0rp/ale) with the `eclipselsp` or `javalsp` LSP linter to get
+this functionality.
 
 
 ------------------------------------------------------------------------------
@@ -354,25 +354,29 @@ vim to verify your setup:
 ==============================================================================
 5. ALE Integration                                             *vim-android-ale*
 
-This plugin full potential is achieved when used in combination with the super
+This plugin full potential is achieved when used in combination with the
 ALE (https://github.com/w0rp/ale) plugin. When this plugin is installed and
 configured we get additional features:
 
- - ALE with javalsp linter gets support for linting and auto-completing Android
-   dependencies. No configuration required.
- - ALE gains a new `android` linter available for xml, java, kotlin, and groovy
-   files. You need to add `android` to these file types in your |g:ale_linters|
-   configuration.
+ - ALE with eclipselsp (jdtls) or javalsp linter gets support for
+   linting, auto-completing, import, and go to definition of Android
+   dependencies.
+ - ALE gains a new `android` linter available for xml, java, kotlin, and
+   groovy files. You need to add `android` to these file types in your
+   |g:ale_linters| configuration.
  - vim-android benefits from all linters/fixers available in ALE like
    checkstyle, google_format, etc.
  - vim-android benefits from ALE auto-completion for java/kotlin files.
 
 Example configuration for best ALE/vim-android combination:
 >
+    let g:gradle_loclist_show = 0
+    let g:gradle_show_signs = 0
+
     let g:ale_linters = {
      \ 'xml': ['android'],
      \ 'groovy': ['android'],
-     \ 'java': ['android', 'checkstyle', 'javalsp'],
+     \ 'java': ['android', 'checkstyle', 'eclipselsp'],
      \ 'kotlin': ['android', 'ktlint', 'languageserver']
      \ }
 <