in your build file (if maven, pom.xml) specify *--release 17* instead of*
--source 17* if you want 17 as the compile and runtime target.
The setting is in the maven compiler settings plugin.
The easiest way to achieve that is setting the property in the properties
section of your pom file
----
<properties>
.
.
<maven.compiler.release>17</maven.compiler.release>
</properties>
----
Met vriendelijke groet,
Pieter van den Hombergh.
Kerboschstraat 12
5913 WH Venlo
On Thu, Oct 31, 2024 at 10:22 AM Arbol One <arbol...@hotmail.ca> wrote:
> In my Netbeans with spcs:
>
> *Product Version: Apache NetBeans IDE 23 *
>
> *Java: 22.0.2; Java HotSpot(TM) 64-Bit Server VM 22.0.2+9-70 *
>
> *Runtime: Java(TM) SE Runtime Environment 22.0.2+9-70 *
>
> *System: Linux version 6.1.0-26-amd64 running on amd64; UTF-8; en_CA (nb)*
>
> I upgraded from OpenJDK 17, the default in Debian to Oracle 22 with specs :
>
>
>
> *java 22.0.2 2024-07-16 Java(TM) SE Runtime Environment (build
> 22.0.2+9-70) Java HotSpot(TM) 64-Bit Server VM (build 22.0.2+9-70, mixed
> mode, sharing)*
>
> After the upgrade I get the following message :
>
>
>
> *warning: [options] location of system modules is not set in conjunction
> with -source 17 not setting the location of system modules may lead to
> class files that cannot run on JDK 17 --release 17 is recommended
> instead of -source 17 -target 17 because it sets the location of system
> modules automatically*
> * 1 warning*
>
> What can I do to avoid this warning?
>
> What setting am I missing?
>
>
> Thanks
> --
> *ArbolOne ™*
> Using Fire Fox and Thunderbird.
> ArbolOne is composed of students and volunteers dedicated to providing
> free services to charitable organizations.
> ArbolOne's development on Java, PostgreSQL, HTML and Jakarta EE is in
> progress [ í ]
>
