Plans to migrate/support to bean validation 3 / jakarta namespace?

[bramklg]

Hi,

I've recently migrated a spring boot 2.7 project to spring boot 3. I was using the conditional validator in the project and that has stopped working. Spring boot 3 uses Hibernate 6.1 which uses version 3 of the validation api.

Are there any plans to migrate this to support the new jakarta namespace / bean validation 3?

[salvadormarcos]

Hello,

Yes, I plan to upgrade to Jakarta BeanValidation 3.

As my project also supports Apache BVal, I was waiting for some Apache release compatible with the new API

[bramklg]

I looked at the commit history of BVal on https://github.com/apache/bval and it isn't really updated a lot except for some dependency updates. They do name bean validator 3.0 though in the readme.

Are you going to wait on Apache BVal? I guess you don't have an e.t.a.?

[salvadormarcos]

In fact, their repository and Jira don't have any information about deadlines.

At first I would wait to migrate both at once and also because I had no update demand. (I don't have statistics about my project's usage) 😅

I can release a Release Candidate version without the BVal, this way you finalize your migration. When BVal releases some release, I release a new version re-adding support

What do you think?

[bramklg]

Sounds good! Thanks!

[salvadormarcos]

Hello @bramklg,

I just released version 2.0.0-rc. Could you test if this release works in your project?

By the way, I took advantage of the migration moment to rename the project's base package. You can see the details on the release page

[bramklg]

@salvadormarcos: tested it out on one of the projects and it works, all tests pass!