Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade Quarkus to 3.8 and switch to @ConfigMapping for the configuration #1998

Open
gsmet opened this issue Feb 14, 2025 · 0 comments
Open

Upgrade Quarkus to 3.8 and switch to @ConfigMapping for the configuration #1998

gsmet opened this issue Feb 14, 2025 · 0 comments

Comments

@gsmet
Copy link
Contributor

gsmet commented Feb 14, 2025

At some point in the future, we will retire the legacy config classes so let's migrate to the new @ConfigMapping infrastructure.

So let's upgrade to Quarkus 3.8 as the minimum version and update to the new config infrastructure.

I will create a PR shortly.
gsmet added a commit to gsmet/blaze-persistence that referenced this issue Feb 14, 2025
@gsmet
[Blazebit#1998] Upgrade to Quarkus 3.8 and switch to @ConfigMapping
3c4d46f 
At some point in the future, we will retire the legacy config classes so
let's migrate to the new @ConfigMapping infrastructure.

I was conservative and only updated to Quarkus 3.8.

Note that there might be more optimizations possible with having all
elements in a single map but I tried to be as less intrusive as possible
as I don't know the codebase.
@gsmet gsmet mentioned this issue Feb 14, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gsmet