Qute message bundles: fix localization of enums

[mkouba]

• support constants with underscores
• fixes Qute message bundle using enum uppercase with words separated by underscores #44866

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit b322dbf.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit b322dbf.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[gsmet]

@mkouba we wanted to make sure before backporting to 3.15 this wouldn't break existing applications i.e. if you have a key defined for an enum that was working prior to this patch, it will still be taken into account?

Thanks.

[mkouba]

@mkouba we wanted to make sure before backporting to 3.15 this wouldn't break existing applications i.e. if you have a key defined for an enum that was working prior to this patch, it will still be taken into account?

I think that previously if a message enum key contained _ or $ the build just failed.

[gsmet]

@mkouba but if you had keys with enums in your resource bundle that worked before, they will still work, right? That's what we wanted to check.

[mkouba]

@mkouba but if you had keys with enums in your resource bundle that worked before, they will still work, right? That's what we wanted to check.

Yes, they should still work.