Gael Abadin

+1

Not sure, but this may have the same root cause as https://github.com/payara/Payara/issues/5902 as they both share a common exception: ``` While attempting to resolve the dependencies of fish.payara.monitoring.runtime.MonitoringConsoleRuntimeImpl errors were...

Love the remove unused keywords/resources/libraries feature. Being able to remove dead imports would be truly awesome on the project I'm currently working on. Let me know if I can be...

+1

( Application level workaround we are introducing until the issue is fixed, just for the custom ValidationExceptionMapper: https://github.com/elcodedocle/payara-sscce/commit/0fd3bc2fbbeadd023eef563e844243b03e36d5d2 )

Hi Elif, > Running `mvn clean verify` on [this project](https://github.com/elcodedocle/payara-sscce/tree/payara-issue-6828) will deploy and run tests on the Payara version specified in the pom.xml file. ```bash git clone --single-branch --branch payara-issue-6828...

Evidence from running the reproducer: Before 6.2004.1 (E.g. Payara 6.2023.12), we get the expected `com.example.payara.hello.ValidationExceptionMapper`: Since 6.2004.1, we get the default `org.glassfish.jersey.server.validation.internal.ValidationExceptionMapper` instead: