Hibernate Validator 4.3.0.Alpah1 release notes

gistfile1.txt

A question which came up recently a lot was the question about the release plan for Hibernate 
Validator 4.3. It is time for an answer.

I used to say that Validator 4.3 will align with Bean Validation 1.1, incorporating any changes 
required for this specification update. Work on BV 1.1 is still in full swing and it is still time
to raise your voice for your long missed validation feature. Check out 
[beanvalidation.org=>http://beanvalidation.org/] for information.

Back to Hibernate Validator though. Over the last few months we incorporated a bunch of useful
changes and bug fixes into the code base. For example all string based *ConstraintValidator*s 
work now on any subclass of *CharSequence* ([HV-502=>https://hibernate.onjira.com/browse/HV-502]) 
and the email validator now supports [internationalized domain names=>http://en.wikipedia.org/wiki/Internationalized_domain_name] 
([HV-472=>https://hibernate.onjira.com/browse/HV-472], Java 6 required). Or check out the new 
generic MOD11 constraint ([HV-491=>https://hibernate.onjira.com/browse/HV-491]) and its application 
in the new constraints CNPJ, CPF and TituloEleitoral (used for Brazilian individual taxpayer
and voting registration numbers). We also have some performance improvements via [HV-550=>https://hibernate.onjira.com/browse/HV-550] and 
[HV-515=>https://hibernate.onjira.com/browse/HV-515].

As you can see quite a bunch of useful changes which we want to release as soon as possible. 
We also want to offer this improvements for users who don't want to upgrade to Bean Validation 1.1
right away (some of the changes will break backwards compatability with Hibernate Validator 4.2).
For this reason we just released Hibernate Validator 4.3.0.Alpha1 with the plan to move to a 
final release as fast as possible. Two more issues are worth mentioning though [HV-481=>https://hibernate.onjira.com/browse/HV-481] and 
[HV-484=>https://hibernate.onjira.com/browse/HV-484].
The former is an switch to [JBoss Logging=>https://community.jboss.org/wiki/JBossLoggingTooling] 
and the latter is the start of a package refactoring which
will (once completed) introduce a clear separation between spi, public and internal api on a 
package level. This change is in accordance with the changes already introduced by the other Hibernate projects.

Hibernate Validator 4.3.0.Alpha1 is available via the [JBoss Maven Repository=>http://repository.jboss.org/nexus] under the GAV 
org.hibernate:hibernate-validator:4.3.0.Alpha1 or via 
[SourceForge=>https://sourceforge.net/projects/hibernate/files/hibernate-validator/4.3.0.Alpha1]. 
The changelog is available [here=>http://hibernate.onjira.com/secure/ReleaseNote.jspa?projectId=10060&version=11240]. Feedback is welcome via
 the [Validator Forum=>https://forum.hibernate.org/viewforum.php?f=9] and the
 [issue tracker=>http://opensource.atlassian.com/projects/hibernate/browse/HV].

As a result, [Hibernate Validator 5=>https://hibernate.onjira.com/browse/HV/fixforversion/11750] 
will become the reference implementation of Bean Validation 1.1.

Thanks to all the people suggesting features and reporting bugs. Special thanks to [George Gastaldi=>https://community.jboss.org/people/gastaldi], 
[Kevin Pollet=>https://community.jboss.org/people/kevinpollet] and [Gunnar Morling=>https://community.jboss.org/people/gunnar.morling] for your continous  
committment. You guys rock!

Enjoy!

Looks good to me. Some minor wording suggestions:

some of the changes will break backwards compatability with Hibernate Validator 4.2

some of the expected changes will break backwards compatibility with Hibernate Validator 4.2

Two more issues are worth mentioning though

Two more issues are worth mentioning though**:**

between spi, public and internal api

between public API/SPI and internal parts

The former is an switch to

The former is the switch to

Maybe also the consequences should be clarified a bit more: no more slf4j binding required, but something equivalent for JBoss logging (if that's the case, I don't know JBoss logging good enough).

continous committment

continuous commitment

Maybe the JavaDoc could be linked for the new constraints?

Looks good to me :-)

We also want to offer this improvements

We also want to offer these improvements

Maybe the JavaDoc could be linked for the new constraints?

+1

Thanks guys. Incorporated your suggestions and release Alpha1