quarkus: Remove in RESTEasy causes for WARNING: An illegal reflective access operation has occurred

2020-06-02 19:26:13,387 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [agroal, cdi, hibernate-orm, hibernate-orm-panache, hibernate-validator, jdbc-mysql, narayana-jta, rest-client, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-fault-tolerance, smallrye-health, smallrye-openapi, swagger-ui]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.resteasy.microprofile.client.header.ComputedHeaderValueFiller (jar:file:/Users/sam/.m2/repository/org/jboss/resteasy/resteasy-client-microprofile/4.5.3.Final/resteasy-client-microprofile-4.5.3.Final.jar!/) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class)
WARNING: Please consider reporting this to the maintainers of org.jboss.resteasy.microprofile.client.header.ComputedHeaderValueFiller
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

I am facing this warnings with JDK 11.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 8
Comments: 17 (14 by maintainers)

Most upvoted comments

On Quarkus 1.8.1 we are still seeing this error. Now that the mentioned issue is fixed at resteasy, can this also be fixed in Quarkus?

wjglerum on Sep 24, 2020

@geoand did you know what is the dependency for this library? Because I didn’t add Yasson to the project.

Would you have any clue?

    implementation 'io.quarkus:quarkus-jdbc-postgresql'
    implementation 'io.quarkus:quarkus-hibernate-orm-panache'
    implementation 'io.quarkus:quarkus-resteasy-jsonb'
    implementation enforcedPlatform("${quarkusPlatformGroupId}:${quarkusPlatformArtifactId}:${quarkusPlatformVersion}")
    implementation 'io.quarkus:quarkus-resteasy'

    testImplementation 'io.quarkus:quarkus-junit5'
    testImplementation 'io.rest-assured:rest-assured'

edufolly on Jun 4, 2020

@edufolly that is a different manifestation. I suggest you report that to Eclipse Yasson since the fix would need to be made there

geoand on Jun 4, 2020