[jboss-jira] [JBoss JIRA] (WFLY-10825) Upgrade to Hibernate Validator 6.0.12.Final

[Guillaume Smet (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617927#comment-13617927 ] 

Guillaume Smet commented on WFLY-10825:
---------------------------------------

[~jamezp] We run the Bean Validation TCK as part of our standard test suite: standalone and included into WildFly.

This is the short story. For this issue, the story is unfortunately longer: when Apache BVal reported some portability issues a few months ago, we unfortunately introduced a portability issue in the TCK which remained unnoticed because of the very fix we reverted (we removed annotations from a bean as an implemented interface was already defining the constraint annotations -> the bean ended up without any BV annotations except on the interface -> this is exactly the issue we wanted to fix with the initial (slow) patch we just reverted). I fixed the issue in the TCK by adding an annotation (as recommended by the spec for portability) and pushed a new version. I also informed Oracle they should upgrade the TCK in the EE TCK to 2.0.4.Final.

So we should be safe on this matter.

> Upgrade to Hibernate Validator 6.0.12.Final
> -------------------------------------------
>
>                 Key: WFLY-10825
>                 URL: https://issues.jboss.org/browse/WFLY-10825
>             Project: WildFly
>          Issue Type: Component Upgrade
>          Components: Bean Validation
>            Reporter: Guillaume Smet
>            Assignee: Guillaume Smet
>             Fix For: 14.0.0.CR1
>
>
> The changelog is here: https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HV%20AND%20fixVersion%20%3D%206.0.12.Final%20order%20by%20created%20DESC .
> The only changes affecting WildFly are:
>  * https://hibernate.atlassian.net/browse/HV-1645 - CDI integration change
>  * https://hibernate.atlassian.net/browse/HV-1643 - minor Russian translation fix
> the rest are infrastructure changes to run the integration test with latest WF 14 Beta1 (and thus allowing us to run them again with JDK 11) and a fix to our dependencies with JDK 11 (which doesn't affect WF at all).
> The reason of this upgrade is specifically the CDI integration change. It reverts the behavior to what was done prior to 6.0.10.Final due to a regression in the startup time of the CDI applications reported by the Open Liberty team.
> As WF 13 was released with HV 6.0.10.Final, it could potentially change the behavior for people having used the EE8 preview mode. This does not concern EAP as the behavior of HV 6.0.12.Final is the same as the version in previous EAP.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)