All Projects → dansomething → coc-groovy

dansomething / coc-groovy

Licence: EPL-2.0 license
Groovy language extension for coc.nvim

Programming Languages

typescript
32286 projects
shell
77523 projects
Batchfile
5799 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to coc-groovy

vim-setup
👾 My NeoVim configuration for Scala & Haskell development (permanently moved to https://github.com/gvolpe/dotfiles)
Stars: ✭ 31 (+121.43%)
Mutual labels:  nvim, coc
coc-flutter-tools
Rich Flutter development experience for (Neo)vim
Stars: ✭ 51 (+264.29%)
Mutual labels:  nvim, coc
quick.nvim
A very fast Lua based Neovim configuration that uses coc.nvim for intellisense
Stars: ✭ 159 (+1035.71%)
Mutual labels:  nvim, coc
coc-discord-rpc
😎 An awesome and fully customizable coc-extension to get Discord Rich Presence integration with NeoVim.
Stars: ✭ 139 (+892.86%)
Mutual labels:  nvim, coc
move.nvim
Gain the power to move lines and blocks and auto-indent them!
Stars: ✭ 109 (+678.57%)
Mutual labels:  nvim
maven-sources
Apache Maven Sources
Stars: ✭ 59 (+321.43%)
Mutual labels:  maven
xml-maven-plugin
XML Maven Plugin
Stars: ✭ 18 (+28.57%)
Mutual labels:  maven
mvnsh
Maven Shell
Stars: ✭ 50 (+257.14%)
Mutual labels:  maven
structlog.nvim
Structured Logging for nvim, using Lua
Stars: ✭ 33 (+135.71%)
Mutual labels:  nvim
coc-sourcekit
Swift language server extension using sourcekit-lsp for coc.nvim.
Stars: ✭ 61 (+335.71%)
Mutual labels:  coc
aquarium-vim
🌊 Aquarium, a simple vibrant dark theme for vim 🗒
Stars: ✭ 151 (+978.57%)
Mutual labels:  nvim
Telegraph.nvim
Send commands system commands in an elegant way
Stars: ✭ 33 (+135.71%)
Mutual labels:  nvim
dotfiles
This is what I use to get things done!
Stars: ✭ 59 (+321.43%)
Mutual labels:  nvim
nvim
Personal neovim config
Stars: ✭ 24 (+71.43%)
Mutual labels:  nvim
coc-volar
Volar (Fast Vue Language Support) extension for coc.nvim
Stars: ✭ 143 (+921.43%)
Mutual labels:  coc
database-all
Eloquent ORM for Java 【database-spring-boot-starter】
Stars: ✭ 151 (+978.57%)
Mutual labels:  maven
VickyWarAnalyzer
Victoria II war analyzer. Java 8 + JavaFX + Maven
Stars: ✭ 43 (+207.14%)
Mutual labels:  maven
betca-spring
BETCA (Spring). Back-end con Tecnologías de Código Abierto, versión Java-Spring
Stars: ✭ 27 (+92.86%)
Mutual labels:  maven
billy
An opensource invoicing engine --
Stars: ✭ 28 (+100%)
Mutual labels:  maven
carnotzet
Modular and Re-usable Docker Environments using Maven
Stars: ✭ 44 (+214.29%)
Mutual labels:  maven

coc-groovy

An extension for coc.nvim to enable Groovy language server support.

Quick Start

  1. Download and install a recent Java Development Kit (latest Java 8 is the minimum requirement).
  2. Install this extension by running this command in Vim:
  :CocInstall coc-groovy
  1. This extension is activated when you first open a Groovy file.

Features

  • Maven and Gradle project support
  • Code Completion
  • Find References
  • Go to Definition
  • Highlights
  • Refactor Rename
  • Signature Hover

Available commands

The following coc.nvim commands are available:

  • groovy.project.config.update : This is available when the editor is focused on a Groovy file. It forces project configuration/classpath updates (eg. dependency changes) according to the project build descriptor.

Supported settings

The following settings are supported:

  • groovy.enable : Enable the coc-groovy extension, default: true
  • groovy.java.home : The absolute path to the JDK 8+ home directory. This is used to launch the Groovy language server. Requires a coc server restart.
  • groovy.ls.vmargs : Extra Java VM arguments used to launch the Groovy language server. Requires a coc server restart.
  • groovy.ls.home : The absolute path to the Groovy language server. This would be used instead of the bundled server when specified.
  • groovy.project.referencedLibraries : Configure additional paths (jar file or directory) for referencing libraries in a Groovy project. Note, Maven and Gradle projects will have their classpath automatically added.
  • groovy.trace.server : Traces the communication between the coc-groovy extension and the Groovy language server.

Setting the JDK

The path to the Java Development Kit is searched in the following order:

  1. The groovy.java.home setting in coc.nvim settings (workspace then user settings).
  2. The JDK_HOME environment variable.
  3. The JAVA_HOME environment variable.
  4. The current system path.

License

EPL 2.0, See LICENSE for more information.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].