How can I set this before the whole automatic installation from the image begins?
I only wrote the sd card, inserted it into the rpi and waited until it was done. Then sshed into the rpi and openhabian 5 was installed.
read the docs. Mount partition on windows and edit openhabian.conf set debugmode=maximum
EDIT: cannot reproduce.
For me, installing the image from Raspi imager results in OH4 with OpenJDK 17
I did it now again (including debugmode on maximum) and I have to confirm, Markus, that all of sudden it does work 
. Java is on 21 temurin and also now, due to not having trixie in the repos anymore also influx db got installed with an issue.
I agree that we should make Temurin 21 the default install until openJDK 21 reaches stable from Debian. That change has been made for the moment.
Is it possible to use the profile j17 in VSCode too?
Where do I find it and how can I add it to VSCode?
I have users running openhab 4.3 who are willing to test my code but I do not dare to ask them to switch to Java 21 on their systems.
I guess the learning curve for switching my developement from VSCode to ecplise would be very flat in the beginning ???
Absolutely. Basically it is just a maven parameter so you can setup your own maven command. I‘m usually too lazy for that so I just use one of the regular maven build commands (install) and then use the terminal to open up the command again (arrow up) and add the parameters I want and run the command again.
Funny, I just installed Java version 21.0.6 (Temurin-21.0.6+7) on a raspberry pi 5 this morning using the regular instructions for Debian:
It worked fine, just need to modify some of the commands like ‘tee’ which need to be run using sudo.
I’m still using OH 4.3.3 but everything seems to be working fine, and may have even solved a persistent time/clock related bug. Not confirmed yet.
I am using the command line too.
After updating Maven and Java to the current version:
mvn --version
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: D:\Prog\apache-maven-3.9.9
Java version: 21.0.6, vendor: Oracle Corporation, runtime: D:\Prog\Java\jdk-21
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"
compiling with:
mvn install clean -Pj17 -Dohc.version=4.3.0
gives:
[ERROR] Unknown lifecycle phase ".version=4.3.0". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: pre-clean, clean, post-clean, validate,...
Any suggestion what I have to do?
Will switching from Oracle Java to Temurin help?
Far from an expert, but I think the -Dohc.version=4.3.0 only works in the openhab addons repository. This worked this am mvn clean install -pl :org.openhab.binding.mideaac -Dohc.version=4.3.0 -Pj17
C:\Users\Robert\GitHub\openhab-addons>mvn --version
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: C:\Program Files (x86)\Maven\apache-maven-3.9.9
Java version: 21.0.4, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-21
Default locale: en_US, platform encoding: UTF-8
OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"
I actually made a jar with the regular mvn clean install, from the 4.3.x branch, and it works. But you must switch to that branch.
But I’m far from an expert (or even an intermediate), so my advice is not worth much, I’m afraid.
@chilobo just tried this in bundles/org.openhab.binding.knx, and it still works on current main branch (5.x).
Windows, Maven 3.9.9.
The error message looks like there was a space between ohc and .version. At least, Maven did not properly recognise it as the name of a define.
Well, the parameter
-Dohc.version=4.3.0
did not work. So I just tried it with
mvn clean install -Pj17
This got me a version 5.0.0-SNAPSHOT which I could use locally in the addon-directory without problems. That’s good enough for testing purposes!
Thanks a lot for helping me!