Releases: vespa-engine/vespa
Vespa Language Server 2.0.11
The Language-server for Vespa schemas
Use the jar file to integration the language server into your favorite editor.
For Visual Studio Code and IntelliJ the language server should also be available in the marketplace for the editor.
Schema Language Server in Neovim
Requirements
Requires java to be excutable on the system.
Optional: lspconfig plugin for nvim.
Installation
Download schema-language-server-jar-with-dependencies.jar
.
Using lspconfig
Register .sd
and .profile
as filetypes (in init.lua
):
vim.filetype.add {
extension = {
profile = 'sd',
sd = 'sd'
}
}
Create a config for schema language server (in init.lua
):
local lspconfig = require "lspconfig"
local configs = require "lspconfig.configs"
if not configs.schemals then
configs.schemals = {
default_config = {
filetypes = { 'sd' },
cmd = { 'java', '-jar', '/path/to/schema-language-server-jar-with-dependencies.jar' },
root_dir = lspconfig.util.root_pattern('.')
},
}
end
lspconfig.schemals.setup{
-- optional on_attach function for setting keybindings etc.
on_attach = function(client, bufnr)
-- local opts = {buffer = bufnr, remap = false}
-- vim.keymap.set("n", "gd", function() vim.lsp.buf.definition() end, opts)
end
}
Manual Installation
If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.
Vespa CLI 8.408.12
The command-line tool for Vespa.ai.
Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.
See Vespa documentation and getting started with Vespa
CLI.
Run make
to build and test - make sure to use go 1.18 or higher.
Vespa CLI 8.405.15
The command-line tool for Vespa.ai.
Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.
See Vespa documentation and getting started with Vespa
CLI.
Run make
to build and test - make sure to use go 1.18 or higher.
Vespa Language Server 2.0.9
The Language-server for Vespa schemas
Use the jar file to integration the language server into your favorite editor.
For Visual Studio Code and IntelliJ the language server should also be available in the marketplace for the editor.
Schema Language Server in Neovim
Requirements
Requires java to be excutable on the system.
Optional: lspconfig plugin for nvim.
Installation
Download schema-language-server-jar-with-dependencies.jar
.
Using lspconfig
Register .sd
and .profile
as filetypes (in init.lua
):
vim.filetype.add {
extension = {
profile = 'sd',
sd = 'sd'
}
}
Create a config for schema language server (in init.lua
):
local lspconfig = require "lspconfig"
local configs = require "lspconfig.configs"
if not configs.schemals then
configs.schemals = {
default_config = {
filetypes = { 'sd' },
cmd = { 'java', '-jar', '/path/to/schema-language-server-jar-with-dependencies.jar' },
root_dir = lspconfig.util.root_pattern('.')
},
}
end
lspconfig.schemals.setup{
-- optional on_attach function for setting keybindings etc.
on_attach = function(client, bufnr)
-- local opts = {buffer = bufnr, remap = false}
-- vim.keymap.set("n", "gd", function() vim.lsp.buf.definition() end, opts)
end
}
Manual Installation
If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.
Vespa Language Server 2.0.10
The Language-server for Vespa schemas
Use the jar file to integration the language server into your favorite editor.
For Visual Studio Code and IntelliJ the language server should also be available in the marketplace for the editor.
Schema Language Server in Neovim
Requirements
Requires java to be excutable on the system.
Optional: lspconfig plugin for nvim.
Installation
Download schema-language-server-jar-with-dependencies.jar
.
Using lspconfig
Register .sd
and .profile
as filetypes (in init.lua
):
vim.filetype.add {
extension = {
profile = 'sd',
sd = 'sd'
}
}
Create a config for schema language server (in init.lua
):
local lspconfig = require "lspconfig"
local configs = require "lspconfig.configs"
if not configs.schemals then
configs.schemals = {
default_config = {
filetypes = { 'sd' },
cmd = { 'java', '-jar', '/path/to/schema-language-server-jar-with-dependencies.jar' },
root_dir = lspconfig.util.root_pattern('.')
},
}
end
lspconfig.schemals.setup{
-- optional on_attach function for setting keybindings etc.
on_attach = function(client, bufnr)
-- local opts = {buffer = bufnr, remap = false}
-- vim.keymap.set("n", "gd", function() vim.lsp.buf.definition() end, opts)
end
}
Manual Installation
If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.
Vespa CLI 8.403.12
The command-line tool for Vespa.ai.
Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.
See Vespa documentation and getting started with Vespa
CLI.
Run make
to build and test - make sure to use go 1.18 or higher.
Vespa Language Server 2.0.6
Vespa language server.
Schema Language Server in Neovim
Requirements
Requires java to be excutable on the system.
Optional: lspconfig plugin for nvim.
Installation
Download vespa-language-server_2.0.6.jar
.
Using lspconfig
Register .sd
and .profile
as filetypes (in init.lua
):
vim.filetype.add {
extension = {
profile = 'sd',
sd = 'sd'
}
}
Create a config for schema language server (in init.lua
):
local lspconfig = require "lspconfig"
local configs = require "lspconfig.configs"
if not configs.schemals then
configs.schemals = {
default_config = {
filetypes = { 'sd' },
cmd = { 'java', '-jar', '/path/to/vespa-language-server_2.0.6.jar' },
root_dir = lspconfig.util.root_pattern('.')
},
}
end
lspconfig.schemals.setup{
-- optional on_attach function for setting keybindings etc.
on_attach = function(client, bufnr)
-- local opts = {buffer = bufnr, remap = false}
-- vim.keymap.set("n", "gd", function() vim.lsp.buf.definition() end, opts)
end
}
Manual Installation
If you don't want to use lspconfig you can refer to the LSP documentation for Neovim for manually registering the server.
Vespa CLI 8.391.23
The command-line tool for Vespa.ai.
Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.
See Vespa documentation and getting started with Vespa
CLI.
Run make
to build and test - make sure to use go 1.18 or higher.
Vespa CLI 8.387.10
The command-line tool for Vespa.ai.
Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.
See Vespa documentation and getting started with Vespa
CLI.
Run make
to build and test - make sure to use go 1.18 or higher.
Vespa CLI 8.371.16
The command-line tool for Vespa.ai.
Use it on Vespa instances running locally, remotely or in the cloud.
Prefer web service API's to this in production.
See Vespa documentation and getting started with Vespa
CLI.
Run make
to build and test - make sure to use go 1.18 or higher.