Put this bash script into the appropriate location

[KOLANICH]

It'd be nice to include it into the prebuilt packages. It makes starting the server easier.

#!/usr/bin/env bash

set -e;

CD=`dirname "${BASH_SOURCE[0]}"`;  # current directory
CD=`realpath $CD`;
echo "CD: $CD";
echo "Args: $@"

SERVER=$CD;  # path to language server dir. Useful, when utilising this script for other distributions of this language server
PLUGINS=$SERVER/plugins;
LAUNCHER=$PLUGINS/$(ls -1 "$PLUGINS" | grep -P "org\\.eclipse\\.equinox\\.launcher_.+\\.jar");
#LAUNCHER=/usr/share/maven-repo/org/eclipse/equinox/org.eclipse.equinox.launcher/debian/org.eclipse.equinox.launcher-debian.jar;
#LOMBOK="/usr/share/maven-repo/org/projectlombok/lombok/debian/lombok-debian.jar"
echo $LAUNCHER;

#-javaagent:$LOMBOK
#-Dsyntaxserver=true
java -jar $LAUNCHER -- --add-modules=ALL-SYSTEM --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED -Declipse.application=org.eclipse.jdt.ls.core.id1 -Dosgi.bundles.defaultStartLevel=4 -Declipse.product=org.eclipse.jdt.ls.core.product -Dosgi.checkConfiguration=true -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true -Dfile.encoding=UTF-8 -DwatchParentProcess=true -Xmx1G -XX:+UseG1GC -XX:+UseStringDeduplication -configuration $SERVER/config_linux $@
#-data /tmp/jdt_ws/%{ActiveProject:Name} - add this arg into the start up args in your IDE. %{ActiveProject:Name} is the var of Qt Creator, other IDEs hase other vars.
#-Dosgi.sharedConfiguration.area=#{etc}/jdtls

[rgrunber]

We do have a section on the wiki page for starting the language server from the command line : https:/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line . It goes into some detail about the various options.

[KOLANICH]

I know. But it is useful to have a ready-to-use script (that can also be customized if needed).

[rgrunber]

I guess I don't really disagree with this. After all, I have a separate shell script locally I've used to launch JDT-LS from commandline and stored the specific options in a shell script. The tricky part is getting and testing something for Windows, Mac, Linux.

On top of this, each client (that implements JDT-LS may have their own way of connecting made available. For example : https:/redhat-developer/vscode-java/blob/master/CONTRIBUTING.md#running-everything , so I'd probably want to keep the scripts in here as simple as possible.

[schrieveslaach]

I'm trying to create a brew formula to make the installation on MacOS easier (see Homebrew/homebrew-core#92550) and one of the maintainers ask for such a scripts

Why doesn't upstream ship a script that sets this because this seems very fragile

The brew formula would solve one of @rgrunber concerns. This would test jdtls on MacOS at least when updating to a new version.

But the process of creating the brew formula raised another question: why is it necessary that the configuration must be writable: >The configuration area at '/usr/local/etc/jdtls' is not writable. Please choose a writable location using the '-configuration

[schrieveslaach]

You can observe the configuration error here

[schrieveslaach]

I solved the read-only configuration issue by adding -Dosgi.checkConfiguration=true -Dosgi.sharedConfiguration.area=#{etc}/jdtls -Dosgi.sharedConfiguration.area.readOnly=true -Dosgi.configuration.cascaded=true as Java properties. These properties make the execution of jdtls package manager friendly and should be included in the script as well.

[KOLANICH]

Thanks, added.