Problems starting xeres from eclipse

[naturzukunft]

Hi there,
i was able to start xeres from command line on my local system and on a remote system. Chat is working fine !
I like, what i see until now.
But now i want to start the local instance in eclipse to be able to run it in debug mode.
I was following that howTo: https://github.com/zapek/Xeres/wiki/Eclipse but if i run the task xeres is not really starting.

Eclipse console output:

Working Directory: /home/naturzukunft/git/Xeres
Gradle user home: /home/naturzukunft/.gradle
Gradle Distribution: Gradle wrapper from target build
Gradle Version: 9.0.0
Java Home: /home/naturzukunft/.sdkman/candidates/java/8.0.452-tem/jre
JVM Arguments: None
Program Arguments: None
Build Scans Enabled: false
Offline Mode Enabled: false
Gradle Tasks: bootRun 

unfortunately i did not know gradle.

[naturzukunft]

ups, jre 8. i will change that

[naturzukunft]

Working Directory: /home/naturzukunft/git/Xeres
Gradle user home: /home/naturzukunft/.gradle
Gradle Distribution: Gradle wrapper from target build
Gradle Version: 9.0.0
Java Home: /home/naturzukunft/.sdkman/candidates/java/21.0.2-open
JVM Arguments: None
Program Arguments: None
Build Scans Enabled: false
Offline Mode Enabled: false
Gradle Tasks: bootRun 

Configuration on demand is an incubating feature.
Parallel Configuration Cache is an incubating feature.
Calculating task graph as no cached configuration is available for tasks: bootRun 

> Configure project :ui
Project :ui => no module-info.java found

[Incubating] Problems report is available at: file:///home/naturzukunft/git/Xeres/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

* What went wrong:
Cannot locate matching tasks for an empty path. The path should include a task name (for example ':help' or 'help').

* Try:
> Run gradle tasks to get a list of available tasks.
> For more on name expansion, please refer to https://docs.gradle.org/9.0.0/userguide/command_line_interface.html#sec:name_abbreviation in the Gradle documentation.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

BUILD FAILED in 483ms
Configuration cache entry stored.

[zapek]

Sorry, I don't really use Eclipse. The tutorial was written the last time I ran it on a VM and I don't even manage to do a proper checkout with it now.

The error means that somehow it doesn't pass the task name properly but it's weird because it's displayed as Gradle Tasks: bootRun. Perhaps double check the Gradle configuration in the workspace.

[zapek]

I finally got it to work with Eclipse. Same parameters as you, except it doesn't complain about some empty path. I wouldn't recommend to use Eclipse though, it was a pain to install.

[naturzukunft]

Ok, i created now a new Eclipse workspace.
I'm using

Spring Tools for Eclipse
Version: 4.31.0.RELEASE
Build Id: 202506052058
Revision: 9a6a935db55fa28327f8695e28f43fd35a568c31

• Open Import dialog "File -> Import"
• Choose "Existing Gradle Project"
• As project root directory choose the location where you checked out xeres
• click "Finish"

Your worcspace should look like that:

Open the "Gradle Tasks" View and select "Xeres-> app -> application -> bootRun"
Right click "Run Gradle Task"

Mistakes

Although my local Spring version is actually the same as on my remote server, I experienced strange, seemingly inconsistent behavior when setting the JRE. However, after setting JAVA_HOME to 21.0.2-open in the project's Gradle settings, xeres started on both Eclipse instances and I was able to exchange messages between the two.

-> check the eclipse console after running the gradle task "bootRun" and be sure, that it shows the correct JAVA_HOME!

I haven't debugged it yet!

[naturzukunft]

Puh, somehow i know why i didn't like gradle ;-)

Debugging

In Eclipse create a new Debug Config:

run on command line ./gradlew bootRun --debug-jvm

The gradle app start process is waiting for the remote debugger. Start the Debug Configuration in Eclipse, then the gradle app start process is resuming and you are able to debug.