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.

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

Jakarta Beans Validation version: 3.0, 3.2 or 4.0? #8392

Closed
hyder opened this issue Feb 16, 2024 · 2 comments · Fixed by #9038
Closed

Jakarta Beans Validation version: 3.0, 3.2 or 4.0? #8392

hyder opened this issue Feb 16, 2024 · 2 comments · Fixed by #9038
Assignees
Labels
4.x Version 4.x

Comments

@hyder
Copy link

hyder commented Feb 16, 2024

Environment Details

  • Helidon Version: 4.0.5
  • Helidon MP
  • JDK version: 21
  • OS:
  • Docker version (if applicable):

Problem Description

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?

Steps to reproduce

Generate a new Helidon MP project and inspect the beans.xml

@barchetta
Copy link
Member

For reference, the last time we updated: #3697

@m0mus m0mus added the 4.x Version 4.x label Feb 22, 2024
@ljnelson
Copy link
Member

Note that the specification in question is CDI, not Jakarta Validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x Version 4.x
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants