Final field flavour in class org.verapdf.pdfa.validation.profiles.ValidationProfileImp has been mutated reflectively by class com.sun.xml.bind.v2.runtime.reflect.Accessor$FieldRefl ection in unnamed module @34340fab

[cfr42]

I currently get a warning each time I run verapdf and, according to the content, this will become an error at some point.

$ verapdf --version
WARNING: Final field flavour in class org.verapdf.pdfa.validation.profiles.ValidationProfileImp
l has been mutated reflectively by class com.sun.xml.bind.v2.runtime.reflect.Accessor$FieldRefl
ection in unnamed module @34340fab (file:/usr/share/verapdf/bin/cli-1.30.1.jar)
WARNING: Use --enable-final-field-mutation=ALL-UNNAMED to avoid a warning
WARNING: Mutating final fields will be blocked in a future release unless final field mutation 
is enabled
veraPDF 1.30.1
Built: Fri Apr 17 13:26:00 BST 2026
Developed and released by the veraPDF Consortium.
Funded by the PREFORMA project.
Released under the GNU General Public License v3
and the Mozilla Public License v2 or later.

Note that I tried to figure out if this had been corrected in the development code, but abjectly failed, so I apologise if this issue has already been corrected there.

[bdoubrov]

@cfr42 thanks a lot for bringing this up. As I understand this warning is shown in case of Java 26+. We'll address this issue in the next 1.32 release. For now, I think, the suggested JAVA CLI property --enable-final-field-mutation=ALL-UNNAMED is the only workaround. It can be added manually into verapdf.sh or verapdf.bat (if you are on Windows) script that launches veraPDF CLI.

[cfr42]

@bdoubrov Thanks for the very fast response. For now I am just ignoring the warning as it does not really do any harm. I reported this in the hope it would get fixed before it turns into an error, though now you have provided a fix which I can use even if that happens before 1.32, which is even better.

[I tend to see warnings early as I'm on Arch.]