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
[BUG] Other handling of custom javax validations since 1.18.10 #2282
Comments
I encountered the same problem! |
Seems to be still an issue, probably happened when I moved from |
any chances to get it fixed? |
It looks like |
Same issue for me, did anyone find out the solution? |
This does not appear to solve the issue. |
This worked for me
not only I had to put |
After Increasing the lombok version from 1.18.8 to 1.18.10 one Junit test doesn't work anymore which tests the javax validation.
In the test, following exception is thrown:
javax.validation.ValidationException: HV000187: When using type annotation constraints on parameterized iterables or map @Valid must be used.
I could find out, that the problem is our custom annotation "NotNullEntry"
In the Test an object is tested which has following annotation. In the Test, the object is just created as an new instance not with the lombok builder.
NotNullEntry is a custom annotation and is defined like following:
Further Details:
Lombok Version: 1.18.10
IDE: Intellij 20019.2.4
Lombok Plugin Version: 0.27-2019.2
The Test:
The text was updated successfully, but these errors were encountered: