RFR: 8353835: Implement JEP 500: Prepare to Make Final Mean Final [v10]

[Alan Bateman]

On Mon, 10 Nov 2025 19:26:25 GMT, Chen Liang <liach at openjdk.org> wrote:

>> Alan Bateman has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 45 commits:
>> 
>>  - Merge branch 'master' into JDK-8353835
>>  - Fix typo in test comment
>>  - Merge branch 'master' into JDK-8353835
>>  - Merge branch 'master' into JDK-8353835
>>  - Suppress warnings from some tests
>>  - Change -Xcheck:jni to be warning rather than fatal error
>>  - Merge branch 'master' into JDK-8353835
>>  - Simplify filter
>>  - Merge branch 'master' into JDK-8353835
>>  - Update Xcheck:jni description
>>  - ... and 35 more: https://git.openjdk.org/jdk/compare/066810c8...6671ae02
>
> test/jdk/java/lang/reflect/Field/mutateFinals/cli/CommandLineTest.java line 234:
> 
>> 232:     @Test
>> 233:     void testSetPropertyToAllow() throws Exception {
>> 234:         test("setSystemPropertyToAllow+testFieldSetInt")
> 
> I thought this was setting the property before the VM boot. Can we have another test that does something like:
> 
> test("testFieldSetInt", "-Djdk.module.illegal.final.field.mutation=allow")
> 
> Which I think is closer to what @vy asks for.

The test sets the internal property at runtime in the launched VM. You are right that another test could launch with the internal property set on the command line with -D.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/25115#discussion_r2514460463