Thanks, I wasn’t aware of the id. Seems that isn’t documented well anywhere. At least I do not find that information anywhere.
Apart from that, as I said, the issue was local. I forgot to add the maven-toolchains-plugin to that specific build. After adding it,
the message is gone in the log.
But still I think the message is not 100% correct. I now understand that it can not find a toolchain, as the plugin is missing. But why
is it stating JAVA_HOME is not set?
Anyhow, that is complaining on a high level. It is only an information and the build works. Just a not so good user experience, as it
probably creates some confusion.
Mit freundlichen Grüßen / Best regards
Dirk Fauth
Cross-Domain Computing Solutions, Cross Automotive Platforms - System, Software and Tools Engineering Engineering Software Methods and Tools1 (XC-ECO/ESM1)
Robert Bosch GmbH | Postfach 30 02 20 | 70442 Stuttgart |
GERMANY | www.bosch.com
Tel. +49 711 811-57819 | Telefax +49 711 811 |
Dirk.Fauth@xxxxxxxxxxxx
Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; Geschäftsführung: Dr. Stefan Hartung,
Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus Heyn, Rolf Najork
Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx> Im Auftrag von
Michael Keppler
Gesendet: Dienstag, 5. April 2022 19:45
An: tycho-dev@xxxxxxxxxxx
Betreff: Re: [tycho-dev] Breaking change in 2.7.0?
Am 05.04.2022 um 08:15 schrieb Fauth Dirk (XC-ECO/ESM1) via tycho-dev:
"Could not find the Toolchain nor JAVA_HOME, trying java from PATH instead"
You toolchain.xml _must_ contain exactly this (with the right id of course). The version is not sufficient.
<provides>
<id>JavaSE-16
</id>
</provides>