We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
When creating a new project, we notice that Helidon is still using Jakarta Beans 3.0:
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="https://jakarta.ee/xml/ns/jakartaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee https://jakarta.ee/xml/ns/jakartaee/beans_3_0.xsd" version="3.0" bean-discovery-mode="annotated"> </beans>
Given there are later versions of the Beans specs (3.2, 4.0), should we upgrade to later versions and should the mp archetype also update its version?
Generate a new Helidon MP project and inspect the beans.xml
The text was updated successfully, but these errors were encountered:
For reference, the last time we updated: #3697
Sorry, something went wrong.
Note that the specification in question is CDI, not Jakarta Validation.
ljnelson
Successfully merging a pull request may close this issue.
Environment Details
Problem Description
When creating a new project, we notice that Helidon is still using Jakarta Beans 3.0:
Given there are later versions of the Beans specs (3.2, 4.0), should we upgrade to later versions and should the mp archetype also update its version?
Steps to reproduce
Generate a new Helidon MP project and inspect the beans.xml
The text was updated successfully, but these errors were encountered: