From javalists at cbfiddle.com  Wed Feb  4 19:02:50 2026
From: javalists at cbfiddle.com (Alan Snyder)
Date: Wed, 4 Feb 2026 11:02:50 -0800
Subject: problems using --enable-native-access
Message-ID: <3C8BF32A-7878-445C-95B0-CB94F49F0F41@cbfiddle.com>

I started trying to use ?enable-native-access but ran into a problem.

I have some (test) programs that I run with many different JDKs. The problem is that giving ?enable-native-access to an old JDK is a fatal error.

Is there some way to perform this configuration that does not crash an older JDK?

A system property, perhaps?


From tjwatson at us.ibm.com  Wed Feb  4 19:58:33 2026
From: tjwatson at us.ibm.com (Thomas Watson)
Date: Wed, 4 Feb 2026 19:58:33 +0000
Subject: problems using --enable-native-access
In-Reply-To: <3C8BF32A-7878-445C-95B0-CB94F49F0F41@cbfiddle.com>
References: <3C8BF32A-7878-445C-95B0-CB94F49F0F41@cbfiddle.com>
Message-ID: <PH7PR15MB6429AF0A76A00217BACFEBBBF598A@PH7PR15MB6429.namprd15.prod.outlook.com>

Try using the JVM option:

 -XX:+IgnoreUnrecognizedVMOptions

Tom
________________________________
From: jigsaw-dev <jigsaw-dev-retn at openjdk.org> on behalf of Alan Snyder <javalists at cbfiddle.com>
Sent: Wednesday, February 4, 2026 1:02 PM
To: jigsaw-dev at openjdk.org <jigsaw-dev at openjdk.org>
Subject: [EXTERNAL] problems using --enable-native-access

I started trying to use ?enable-native-access but ran into a problem.

I have some (test) programs that I run with many different JDKs. The problem is that giving ?enable-native-access to an old JDK is a fatal error.

Is there some way to perform this configuration that does not crash an older JDK?

A system property, perhaps?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jigsaw-dev/attachments/20260204/f8f3a947/attachment.htm>

From javalists at cbfiddle.com  Sat Feb  7 16:18:08 2026
From: javalists at cbfiddle.com (Alan Snyder)
Date: Sat, 7 Feb 2026 08:18:08 -0800
Subject: problems using --enable-native-access
In-Reply-To: <PH7PR15MB6429AF0A76A00217BACFEBBBF598A@PH7PR15MB6429.namprd15.prod.outlook.com>
References: <3C8BF32A-7878-445C-95B0-CB94F49F0F41@cbfiddle.com>
 <PH7PR15MB6429AF0A76A00217BACFEBBBF598A@PH7PR15MB6429.namprd15.prod.outlook.com>
Message-ID: <C8F17BE1-54DE-4B44-B0BB-0CC1A4023723@cbfiddle.com>

That worked. Thank you.

  Alan

> On Feb 4, 2026, at 11:58?AM, Thomas Watson <tjwatson at us.ibm.com> wrote:
> 
> Try using the JVM option:
> 
>  -XX:+IgnoreUnrecognizedVMOptions
> 
> Tom
> From: jigsaw-dev <jigsaw-dev-retn at openjdk.org> on behalf of Alan Snyder <javalists at cbfiddle.com>
> Sent: Wednesday, February 4, 2026 1:02 PM
> To: jigsaw-dev at openjdk.org <jigsaw-dev at openjdk.org>
> Subject: [EXTERNAL] problems using --enable-native-access
>  
> I started trying to use ?enable-native-access but ran into a problem.
> 
> I have some (test) programs that I run with many different JDKs. The problem is that giving ?enable-native-access to an old JDK is a fatal error.
> 
> Is there some way to perform this configuration that does not crash an older JDK?
> 
> A system property, perhaps?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jigsaw-dev/attachments/20260207/652d7109/attachment-0001.htm>