@ConfigMapping not working in 2.4.0.Final, but works in 2.3.1.Final
#20916
Labels
Milestone
Comments
|
Having a look |
|
This actually seems related to the optimization done in #19965. The unused validation is only checking for the actual annotated class, but in this case, the injection point is using a parent class. I'll work on a fix. Sorry for the inconvenience. |
snazy
added a commit
to snazy/nessie
that referenced
this issue
Oct 22, 2021
snazy
added a commit
to snazy/nessie
that referenced
this issue
Nov 3, 2021
snazy
added a commit
to snazy/nessie
that referenced
this issue
Nov 3, 2021
snazy
added a commit
to projectnessie/nessie
that referenced
this issue
Nov 3, 2021
* Bump Quarkus version from 2.4.0.Final to 2.4.1.Final Pulls in quarkusio/quarkus#20940 to fix quarkusio/quarkus#20916 and quarkusio/quarkus#20917 * Revert config-type workaround for Quarkus 2.4.0 * Revert config-mapping workaround for Quarkus 2.4.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We hit the
@ConfigMappingvs.@ConfigPropertieswhen the config's "statically" injected issue again with 2.4.0.Final.dependabot-bump-PR run with code that works w/ Quarlus 2.3.1.Final. Related to #20103
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.4.0.Final
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: