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

[FEATURE] jakarta validation-api JSR 303 #206

Open
2 tasks done
kchaber opened this issue Aug 28, 2024 · 0 comments · May be fixed by #211
Open
2 tasks done

[FEATURE] jakarta validation-api JSR 303 #206

kchaber opened this issue Aug 28, 2024 · 0 comments · May be fixed by #211
Assignees
Labels
enhancement New feature or request

Comments

@kchaber
Copy link

kchaber commented Aug 28, 2024

Why do we need this improvement?

As per JSR 303 the javax.validation has been replaced in favor of jakarta.validation.

How will this change help?

Consistency with the current standard

Screenshots

No response

How could it be implemented/designed?

  • Replace the following maven dependency:
<dependency>
    <groupId>javax.validation</groupId>
    <artifactId>validation-api</artifactId>
    <version>...</version>
</dependency>

with the jakarta substitute:

<dependency>
    <groupId>jakarta.validation</groupId>
    <artifactId>jakarta.validation-api</artifactId>
    <version>...</version>
</dependency>
  • replace the javax. class imports with the jakarta. prefix

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

  • I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue?

None

@kchaber kchaber added the enhancement New feature or request label Aug 28, 2024
@Pakisan Pakisan self-assigned this Aug 28, 2024
Pakisan added a commit that referenced this issue Jan 9, 2025
javax.validation has been replaced with jakarta.validation

Fixes #206
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants