Foivos Zakkak
Foivos Zakkak
@gsmet can you please have a look (or assign someone else who can?). Thanks.
@gsmet this slipped through the cracks can you please have a look?
> @zakkak is this something still worth considering? Given the move to registering the complete metadata for reflection types in https://github.com/oracle/graal/pull/12521 this seems obsolete.
@DudekJakub I see you are using GraalVM, does this issue appear when you compile your application to native or in JVM-mode as well?
Are you [building a native executable](https://quarkus.io/guides/building-native-image)?
cc @vjovanov
I believe the way to fix this is to have Quarkus add the `Enable-Native-Access: ALL-UNNAMED` attribute to the jar manifests (and pass `--enable-native-access=ALL-UNNAMED` to `java` when not using a jar...
> I believe the way to fix this is to have Quarkus add the `Enable-Native-Access: ALL-UNNAMED` attribute to the jar manifests (and pass `--enable-native-access=ALL-UNNAMED` to `java` when not using a...
> Is this a general thing that will work with the various restrictions the JDK is putting in place? That's my so far understanding.
> So we should hide this from the user if possible. How could one achieve that? In runner jars it's easy to achieve through the manifest entry, but in JVM...