From gunnar at hibernate.org  Tue Jul  4 10:26:01 2017
From: gunnar at hibernate.org (Gunnar Morling)
Date: Tue, 4 Jul 2017 16:26:01 +0200
Subject: [bv-dev] Releasing CR 2
Message-ID: <CADGJaX9ccC01BQbq7SXm0xLhu3h8wdM_tynzb84d5BTyJUhWQw@mail.gmail.com>

Hey all,

After last week's Proposed Final Draft, we are almost there for the
submission to the Final Approval Ballot.

I'd like to do a CR 2 release of the spec tomorrow, which is about
adding some clarifications, polishing comments, formatting and things
like that. You can find the complete list of issues here:
https://hibernate.atlassian.net/issues/?jql=project%20%3D%20BVAL%20AND%20fixVersion%20%3D%202.0.0.CR2%20ORDER%20BY%20status%20DESC

During reviews we've also noticed a small set of things that mandated
fixes to the API. These are:

* BVAL-569 [1] - "Remove TYPE from targets of @ConvertGroup for
consistency with @Valid" - @ConvertGroup was accidentally allowed to
be given on type definitions, too (unlike @Valid which it always must
accompany). This has been corrected by removing TYPE from the set of
supported targets; the change is strictly binary and source
compatible, as a) annotation targets are only checked at compile time
but not runtime and b) the newly introduced target of TYPE_USE also
allows the annotation to be given on type definitions; so it's a mere
cosmetic change

* BVAL-689 [2] - "Make @ConvertGroup#from() default to Default.class"
- this simplifies group conversions in the common case where the
default group is converted

* BVAL-674 [3] - "Rename ConstraintDescriptor#validateUnwrappedValue()
into getValueUnwrapping()" - the method name sounded like a "command"
before, whereas the new name makes clear it's a "query" kind of
method; also the members of the returned enum have been adapted to be
in sync with the corresponding Unwrapping payload type names; also
there's a new method ConstraintDescriptor#unwrap(Class), our common
loophole allowing providers to add additional functionality; this
eases exploration of such features and future standardization

Another interesting change is this:

* BVAL-613 [4] - Add an Automatic-Module-Name entry to the JAR
manifest; fixing the module name to "java.validation" as recommended
in the spec appendix when using the reference API JAR as an automatic
module on JPMS

With the CR 2, I consider the spec as feature complete and am only
expecting small changes like typo fixes and the like between CR 2 and
CR 3, the version to be submitted for the Final Approval Ballot. We
got one more week for that, i.e. I'll submit to the FAB on July 11th.

Please use this remaining time for reviewing and pointing out any
remaining glitches (I hope there are none of course :).

Cheers,

--Gunnar

[1] https://hibernate.atlassian.net/browse/BVAL-569
[2] https://hibernate.atlassian.net/browse/BVAL-689
[3] https://hibernate.atlassian.net/browse/BVAL-674
[4] https://hibernate.atlassian.net/browse/BVAL-613

From gunnar at hibernate.org  Wed Jul  5 11:23:01 2017
From: gunnar at hibernate.org (Gunnar Morling)
Date: Wed, 5 Jul 2017 17:23:01 +0200
Subject: [bv-dev] Releasing CR 2
In-Reply-To: <CADGJaX9ccC01BQbq7SXm0xLhu3h8wdM_tynzb84d5BTyJUhWQw@mail.gmail.com>
References: <CADGJaX9ccC01BQbq7SXm0xLhu3h8wdM_tynzb84d5BTyJUhWQw@mail.gmail.com>
Message-ID: <CADGJaX--JR3t1um-xLrEkKDgsm+kkrJyqTAnoZJ+wv3B=HXUgQ@mail.gmail.com>

Hi all,

The CR 2 has been released:

* Announcement:
http://beanvalidation.org/news/2017/07/05/bean-validation-2-0-cr2-is-out/
* Spec: http://beanvalidation.org/2.0/spec/2.0.0.cr2/
* Full Diff: http://beanvalidation.org/2.0/spec/2.0.0.cr2/diff/diff-to-1.1/

As announced earlier, the FAB submission is due early next week.
Please let me know if you have any further comments or remarks. Does
anyone see anything which should be addressed before doing the
submission? If nothing comes up, I'll push the button on Tuesday.

Thanks,

--Gunnar




2017-07-04 16:26 GMT+02:00 Gunnar Morling <gunnar at hibernate.org>:
> Hey all,
>
> After last week's Proposed Final Draft, we are almost there for the
> submission to the Final Approval Ballot.
>
> I'd like to do a CR 2 release of the spec tomorrow, which is about
> adding some clarifications, polishing comments, formatting and things
> like that. You can find the complete list of issues here:
> https://hibernate.atlassian.net/issues/?jql=project%20%3D%20BVAL%20AND%20fixVersion%20%3D%202.0.0.CR2%20ORDER%20BY%20status%20DESC
>
> During reviews we've also noticed a small set of things that mandated
> fixes to the API. These are:
>
> * BVAL-569 [1] - "Remove TYPE from targets of @ConvertGroup for
> consistency with @Valid" - @ConvertGroup was accidentally allowed to
> be given on type definitions, too (unlike @Valid which it always must
> accompany). This has been corrected by removing TYPE from the set of
> supported targets; the change is strictly binary and source
> compatible, as a) annotation targets are only checked at compile time
> but not runtime and b) the newly introduced target of TYPE_USE also
> allows the annotation to be given on type definitions; so it's a mere
> cosmetic change
>
> * BVAL-689 [2] - "Make @ConvertGroup#from() default to Default.class"
> - this simplifies group conversions in the common case where the
> default group is converted
>
> * BVAL-674 [3] - "Rename ConstraintDescriptor#validateUnwrappedValue()
> into getValueUnwrapping()" - the method name sounded like a "command"
> before, whereas the new name makes clear it's a "query" kind of
> method; also the members of the returned enum have been adapted to be
> in sync with the corresponding Unwrapping payload type names; also
> there's a new method ConstraintDescriptor#unwrap(Class), our common
> loophole allowing providers to add additional functionality; this
> eases exploration of such features and future standardization
>
> Another interesting change is this:
>
> * BVAL-613 [4] - Add an Automatic-Module-Name entry to the JAR
> manifest; fixing the module name to "java.validation" as recommended
> in the spec appendix when using the reference API JAR as an automatic
> module on JPMS
>
> With the CR 2, I consider the spec as feature complete and am only
> expecting small changes like typo fixes and the like between CR 2 and
> CR 3, the version to be submitted for the Final Approval Ballot. We
> got one more week for that, i.e. I'll submit to the FAB on July 11th.
>
> Please use this remaining time for reviewing and pointing out any
> remaining glitches (I hope there are none of course :).
>
> Cheers,
>
> --Gunnar
>
> [1] https://hibernate.atlassian.net/browse/BVAL-569
> [2] https://hibernate.atlassian.net/browse/BVAL-689
> [3] https://hibernate.atlassian.net/browse/BVAL-674
> [4] https://hibernate.atlassian.net/browse/BVAL-613

From mbenson at apache.org  Wed Jul  5 13:39:00 2017
From: mbenson at apache.org (Matt Benson)
Date: Wed, 5 Jul 2017 12:39:00 -0500
Subject: [bv-dev] Releasing CR 2
In-Reply-To: <CADGJaX--JR3t1um-xLrEkKDgsm+kkrJyqTAnoZJ+wv3B=HXUgQ@mail.gmail.com>
References: <CADGJaX9ccC01BQbq7SXm0xLhu3h8wdM_tynzb84d5BTyJUhWQw@mail.gmail.com>
	<CADGJaX--JR3t1um-xLrEkKDgsm+kkrJyqTAnoZJ+wv3B=HXUgQ@mail.gmail.com>
Message-ID: <CAE9L6G2vXx_h9T+V3VZEGbX6gWa9uhne=0ThGrm8+2oDvRVXnQ@mail.gmail.com>

What does anyone think about adding #unwrap() to ElementDescriptor?

Matt

On Jul 5, 2017 12:32 PM, "Gunnar Morling" <gunnar at hibernate.org> wrote:

> Hi all,
>
> The CR 2 has been released:
>
> * Announcement:
> http://beanvalidation.org/news/2017/07/05/bean-validation-2-0-cr2-is-out/
> * Spec: http://beanvalidation.org/2.0/spec/2.0.0.cr2/
> * Full Diff: http://beanvalidation.org/2.0/spec/2.0.0.cr2/diff/diff-to-1.
> 1/
>
> As announced earlier, the FAB submission is due early next week.
> Please let me know if you have any further comments or remarks. Does
> anyone see anything which should be addressed before doing the
> submission? If nothing comes up, I'll push the button on Tuesday.
>
> Thanks,
>
> --Gunnar
>
>
>
>
> 2017-07-04 16:26 GMT+02:00 Gunnar Morling <gunnar at hibernate.org>:
> > Hey all,
> >
> > After last week's Proposed Final Draft, we are almost there for the
> > submission to the Final Approval Ballot.
> >
> > I'd like to do a CR 2 release of the spec tomorrow, which is about
> > adding some clarifications, polishing comments, formatting and things
> > like that. You can find the complete list of issues here:
> > https://hibernate.atlassian.net/issues/?jql=project%20%3D%
> 20BVAL%20AND%20fixVersion%20%3D%202.0.0.CR2%20ORDER%20BY%20status%20DESC
> >
> > During reviews we've also noticed a small set of things that mandated
> > fixes to the API. These are:
> >
> > * BVAL-569 [1] - "Remove TYPE from targets of @ConvertGroup for
> > consistency with @Valid" - @ConvertGroup was accidentally allowed to
> > be given on type definitions, too (unlike @Valid which it always must
> > accompany). This has been corrected by removing TYPE from the set of
> > supported targets; the change is strictly binary and source
> > compatible, as a) annotation targets are only checked at compile time
> > but not runtime and b) the newly introduced target of TYPE_USE also
> > allows the annotation to be given on type definitions; so it's a mere
> > cosmetic change
> >
> > * BVAL-689 [2] - "Make @ConvertGroup#from() default to Default.class"
> > - this simplifies group conversions in the common case where the
> > default group is converted
> >
> > * BVAL-674 [3] - "Rename ConstraintDescriptor#validateUnwrappedValue()
> > into getValueUnwrapping()" - the method name sounded like a "command"
> > before, whereas the new name makes clear it's a "query" kind of
> > method; also the members of the returned enum have been adapted to be
> > in sync with the corresponding Unwrapping payload type names; also
> > there's a new method ConstraintDescriptor#unwrap(Class), our common
> > loophole allowing providers to add additional functionality; this
> > eases exploration of such features and future standardization
> >
> > Another interesting change is this:
> >
> > * BVAL-613 [4] - Add an Automatic-Module-Name entry to the JAR
> > manifest; fixing the module name to "java.validation" as recommended
> > in the spec appendix when using the reference API JAR as an automatic
> > module on JPMS
> >
> > With the CR 2, I consider the spec as feature complete and am only
> > expecting small changes like typo fixes and the like between CR 2 and
> > CR 3, the version to be submitted for the Final Approval Ballot. We
> > got one more week for that, i.e. I'll submit to the FAB on July 11th.
> >
> > Please use this remaining time for reviewing and pointing out any
> > remaining glitches (I hope there are none of course :).
> >
> > Cheers,
> >
> > --Gunnar
> >
> > [1] https://hibernate.atlassian.net/browse/BVAL-569
> > [2] https://hibernate.atlassian.net/browse/BVAL-689
> > [3] https://hibernate.atlassian.net/browse/BVAL-674
> > [4] https://hibernate.atlassian.net/browse/BVAL-613
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20170705/4f83a315/attachment.html 

From gunnar at hibernate.org  Wed Jul  5 14:52:56 2017
From: gunnar at hibernate.org (Gunnar Morling)
Date: Wed, 5 Jul 2017 20:52:56 +0200
Subject: [bv-dev] Releasing CR 2
In-Reply-To: <CAE9L6G2vXx_h9T+V3VZEGbX6gWa9uhne=0ThGrm8+2oDvRVXnQ@mail.gmail.com>
References: <CADGJaX9ccC01BQbq7SXm0xLhu3h8wdM_tynzb84d5BTyJUhWQw@mail.gmail.com>
	<CADGJaX--JR3t1um-xLrEkKDgsm+kkrJyqTAnoZJ+wv3B=HXUgQ@mail.gmail.com>
	<CAE9L6G2vXx_h9T+V3VZEGbX6gWa9uhne=0ThGrm8+2oDvRVXnQ@mail.gmail.com>
Message-ID: <CADGJaX_iTehhCUbgRUy5bzwKULWahRA9o8LinpEEEPE6jqWLvg@mail.gmail.com>

Hey Matt,

Would have been nice to have for today's release, I'm a bit reluctant
to doing an API change in the FAB delivery. Do you have specific
descriptor functionality in mind which you'd like to expose in a
provider-specific extension?

--Gunnar


2017-07-05 19:39 GMT+02:00 Matt Benson <mbenson at apache.org>:
> What does anyone think about adding #unwrap() to ElementDescriptor?
>
> Matt
>
> On Jul 5, 2017 12:32 PM, "Gunnar Morling" <gunnar at hibernate.org> wrote:
>>
>> Hi all,
>>
>> The CR 2 has been released:
>>
>> * Announcement:
>> http://beanvalidation.org/news/2017/07/05/bean-validation-2-0-cr2-is-out/
>> * Spec: http://beanvalidation.org/2.0/spec/2.0.0.cr2/
>> * Full Diff:
>> http://beanvalidation.org/2.0/spec/2.0.0.cr2/diff/diff-to-1.1/
>>
>> As announced earlier, the FAB submission is due early next week.
>> Please let me know if you have any further comments or remarks. Does
>> anyone see anything which should be addressed before doing the
>> submission? If nothing comes up, I'll push the button on Tuesday.
>>
>> Thanks,
>>
>> --Gunnar
>>
>>
>>
>>
>> 2017-07-04 16:26 GMT+02:00 Gunnar Morling <gunnar at hibernate.org>:
>> > Hey all,
>> >
>> > After last week's Proposed Final Draft, we are almost there for the
>> > submission to the Final Approval Ballot.
>> >
>> > I'd like to do a CR 2 release of the spec tomorrow, which is about
>> > adding some clarifications, polishing comments, formatting and things
>> > like that. You can find the complete list of issues here:
>> >
>> > https://hibernate.atlassian.net/issues/?jql=project%20%3D%20BVAL%20AND%20fixVersion%20%3D%202.0.0.CR2%20ORDER%20BY%20status%20DESC
>> >
>> > During reviews we've also noticed a small set of things that mandated
>> > fixes to the API. These are:
>> >
>> > * BVAL-569 [1] - "Remove TYPE from targets of @ConvertGroup for
>> > consistency with @Valid" - @ConvertGroup was accidentally allowed to
>> > be given on type definitions, too (unlike @Valid which it always must
>> > accompany). This has been corrected by removing TYPE from the set of
>> > supported targets; the change is strictly binary and source
>> > compatible, as a) annotation targets are only checked at compile time
>> > but not runtime and b) the newly introduced target of TYPE_USE also
>> > allows the annotation to be given on type definitions; so it's a mere
>> > cosmetic change
>> >
>> > * BVAL-689 [2] - "Make @ConvertGroup#from() default to Default.class"
>> > - this simplifies group conversions in the common case where the
>> > default group is converted
>> >
>> > * BVAL-674 [3] - "Rename ConstraintDescriptor#validateUnwrappedValue()
>> > into getValueUnwrapping()" - the method name sounded like a "command"
>> > before, whereas the new name makes clear it's a "query" kind of
>> > method; also the members of the returned enum have been adapted to be
>> > in sync with the corresponding Unwrapping payload type names; also
>> > there's a new method ConstraintDescriptor#unwrap(Class), our common
>> > loophole allowing providers to add additional functionality; this
>> > eases exploration of such features and future standardization
>> >
>> > Another interesting change is this:
>> >
>> > * BVAL-613 [4] - Add an Automatic-Module-Name entry to the JAR
>> > manifest; fixing the module name to "java.validation" as recommended
>> > in the spec appendix when using the reference API JAR as an automatic
>> > module on JPMS
>> >
>> > With the CR 2, I consider the spec as feature complete and am only
>> > expecting small changes like typo fixes and the like between CR 2 and
>> > CR 3, the version to be submitted for the Final Approval Ballot. We
>> > got one more week for that, i.e. I'll submit to the FAB on July 11th.
>> >
>> > Please use this remaining time for reviewing and pointing out any
>> > remaining glitches (I hope there are none of course :).
>> >
>> > Cheers,
>> >
>> > --Gunnar
>> >
>> > [1] https://hibernate.atlassian.net/browse/BVAL-569
>> > [2] https://hibernate.atlassian.net/browse/BVAL-689
>> > [3] https://hibernate.atlassian.net/browse/BVAL-674
>> > [4] https://hibernate.atlassian.net/browse/BVAL-613
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev

From mbenson at apache.org  Wed Jul  5 16:05:40 2017
From: mbenson at apache.org (Matt Benson)
Date: Wed, 5 Jul 2017 15:05:40 -0500
Subject: [bv-dev] Releasing CR 2
In-Reply-To: <CADGJaX_iTehhCUbgRUy5bzwKULWahRA9o8LinpEEEPE6jqWLvg@mail.gmail.com>
References: <CADGJaX9ccC01BQbq7SXm0xLhu3h8wdM_tynzb84d5BTyJUhWQw@mail.gmail.com>
	<CADGJaX--JR3t1um-xLrEkKDgsm+kkrJyqTAnoZJ+wv3B=HXUgQ@mail.gmail.com>
	<CAE9L6G2vXx_h9T+V3VZEGbX6gWa9uhne=0ThGrm8+2oDvRVXnQ@mail.gmail.com>
	<CADGJaX_iTehhCUbgRUy5bzwKULWahRA9o8LinpEEEPE6jqWLvg@mail.gmail.com>
Message-ID: <CAE9L6G3PWG7C8Jp0E+op+PPxEbxy3LhGGqV195a_4QDRfvtTzw@mail.gmail.com>

More for implementation purposes, really ;) NP

Matt

On Wed, Jul 5, 2017 at 1:52 PM, Gunnar Morling <gunnar at hibernate.org> wrote:
> Hey Matt,
>
> Would have been nice to have for today's release, I'm a bit reluctant
> to doing an API change in the FAB delivery. Do you have specific
> descriptor functionality in mind which you'd like to expose in a
> provider-specific extension?
>
> --Gunnar
>
>
> 2017-07-05 19:39 GMT+02:00 Matt Benson <mbenson at apache.org>:
>> What does anyone think about adding #unwrap() to ElementDescriptor?
>>
>> Matt
>>
>> On Jul 5, 2017 12:32 PM, "Gunnar Morling" <gunnar at hibernate.org> wrote:
>>>
>>> Hi all,
>>>
>>> The CR 2 has been released:
>>>
>>> * Announcement:
>>> http://beanvalidation.org/news/2017/07/05/bean-validation-2-0-cr2-is-out/
>>> * Spec: http://beanvalidation.org/2.0/spec/2.0.0.cr2/
>>> * Full Diff:
>>> http://beanvalidation.org/2.0/spec/2.0.0.cr2/diff/diff-to-1.1/
>>>
>>> As announced earlier, the FAB submission is due early next week.
>>> Please let me know if you have any further comments or remarks. Does
>>> anyone see anything which should be addressed before doing the
>>> submission? If nothing comes up, I'll push the button on Tuesday.
>>>
>>> Thanks,
>>>
>>> --Gunnar
>>>
>>>
>>>
>>>
>>> 2017-07-04 16:26 GMT+02:00 Gunnar Morling <gunnar at hibernate.org>:
>>> > Hey all,
>>> >
>>> > After last week's Proposed Final Draft, we are almost there for the
>>> > submission to the Final Approval Ballot.
>>> >
>>> > I'd like to do a CR 2 release of the spec tomorrow, which is about
>>> > adding some clarifications, polishing comments, formatting and things
>>> > like that. You can find the complete list of issues here:
>>> >
>>> > https://hibernate.atlassian.net/issues/?jql=project%20%3D%20BVAL%20AND%20fixVersion%20%3D%202.0.0.CR2%20ORDER%20BY%20status%20DESC
>>> >
>>> > During reviews we've also noticed a small set of things that mandated
>>> > fixes to the API. These are:
>>> >
>>> > * BVAL-569 [1] - "Remove TYPE from targets of @ConvertGroup for
>>> > consistency with @Valid" - @ConvertGroup was accidentally allowed to
>>> > be given on type definitions, too (unlike @Valid which it always must
>>> > accompany). This has been corrected by removing TYPE from the set of
>>> > supported targets; the change is strictly binary and source
>>> > compatible, as a) annotation targets are only checked at compile time
>>> > but not runtime and b) the newly introduced target of TYPE_USE also
>>> > allows the annotation to be given on type definitions; so it's a mere
>>> > cosmetic change
>>> >
>>> > * BVAL-689 [2] - "Make @ConvertGroup#from() default to Default.class"
>>> > - this simplifies group conversions in the common case where the
>>> > default group is converted
>>> >
>>> > * BVAL-674 [3] - "Rename ConstraintDescriptor#validateUnwrappedValue()
>>> > into getValueUnwrapping()" - the method name sounded like a "command"
>>> > before, whereas the new name makes clear it's a "query" kind of
>>> > method; also the members of the returned enum have been adapted to be
>>> > in sync with the corresponding Unwrapping payload type names; also
>>> > there's a new method ConstraintDescriptor#unwrap(Class), our common
>>> > loophole allowing providers to add additional functionality; this
>>> > eases exploration of such features and future standardization
>>> >
>>> > Another interesting change is this:
>>> >
>>> > * BVAL-613 [4] - Add an Automatic-Module-Name entry to the JAR
>>> > manifest; fixing the module name to "java.validation" as recommended
>>> > in the spec appendix when using the reference API JAR as an automatic
>>> > module on JPMS
>>> >
>>> > With the CR 2, I consider the spec as feature complete and am only
>>> > expecting small changes like typo fixes and the like between CR 2 and
>>> > CR 3, the version to be submitted for the Final Approval Ballot. We
>>> > got one more week for that, i.e. I'll submit to the FAB on July 11th.
>>> >
>>> > Please use this remaining time for reviewing and pointing out any
>>> > remaining glitches (I hope there are none of course :).
>>> >
>>> > Cheers,
>>> >
>>> > --Gunnar
>>> >
>>> > [1] https://hibernate.atlassian.net/browse/BVAL-569
>>> > [2] https://hibernate.atlassian.net/browse/BVAL-689
>>> > [3] https://hibernate.atlassian.net/browse/BVAL-674
>>> > [4] https://hibernate.atlassian.net/browse/BVAL-613
>>> _______________________________________________
>>> beanvalidation-dev mailing list
>>> beanvalidation-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev

From gunnar at hibernate.org  Mon Jul 10 09:25:12 2017
From: gunnar at hibernate.org (Gunnar Morling)
Date: Mon, 10 Jul 2017 15:25:12 +0200
Subject: [bv-dev] Submitting to Final Approval Ballot
Message-ID: <CADGJaX9LGxEsp-Xt5f+A=_qyQQo8AZAvkoBqhNLdtqbNEYczLw@mail.gmail.com>

Hi all,

As discussed I'm going to submit the BV 2.0 spec to the JCP for Final
Approval Ballot tomorrow.

Since last week's CR 2, there's one issue that has popped up: BVAL-690
[1] which was to clarify the behaviour of
ConstraintViolation#getLeafBean() for container element constraints.
The change for this is at [2].

If nothing else comes up and I don't hear any objections, I'll submit
the spec tomorrow.

Thanks,

--Gunnar

[1] https://hibernate.atlassian.net/browse/BVAL-690
[2] https://github.com/beanvalidation/beanvalidation-spec/pull/237

From moltenma at gmail.com  Tue Jul 11 03:02:13 2017
From: moltenma at gmail.com (Marco Molteni)
Date: Tue, 11 Jul 2017 09:02:13 +0200
Subject: [bv-dev] Submitting to Final Approval Ballot
In-Reply-To: <CADGJaX9LGxEsp-Xt5f+A=_qyQQo8AZAvkoBqhNLdtqbNEYczLw@mail.gmail.com>
References: <CADGJaX9LGxEsp-Xt5f+A=_qyQQo8AZAvkoBqhNLdtqbNEYczLw@mail.gmail.com>
Message-ID: <CANUPYM25hqaGmcqw0aJJR9k9Z_qpootaTjKHVjKccABKsTO21Q@mail.gmail.com>

Ok :)
Thanks Gunnar and Guillaume!

On Mon, Jul 10, 2017 at 3:25 PM, Gunnar Morling <gunnar at hibernate.org>
wrote:

> Hi all,
>
> As discussed I'm going to submit the BV 2.0 spec to the JCP for Final
> Approval Ballot tomorrow.
>
> Since last week's CR 2, there's one issue that has popped up: BVAL-690
> [1] which was to clarify the behaviour of
> ConstraintViolation#getLeafBean() for container element constraints.
> The change for this is at [2].
>
> If nothing else comes up and I don't hear any objections, I'll submit
> the spec tomorrow.
>
> Thanks,
>
> --Gunnar
>
> [1] https://hibernate.atlassian.net/browse/BVAL-690
> [2] https://github.com/beanvalidation/beanvalidation-spec/pull/237
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20170711/90d1e921/attachment.html 

From gunnar at hibernate.org  Wed Jul 12 06:30:55 2017
From: gunnar at hibernate.org (Gunnar Morling)
Date: Wed, 12 Jul 2017 12:30:55 +0200
Subject: [bv-dev] Submitting to Final Approval Ballot
In-Reply-To: <CANUPYM25hqaGmcqw0aJJR9k9Z_qpootaTjKHVjKccABKsTO21Q@mail.gmail.com>
References: <CADGJaX9LGxEsp-Xt5f+A=_qyQQo8AZAvkoBqhNLdtqbNEYczLw@mail.gmail.com>
	<CANUPYM25hqaGmcqw0aJJR9k9Z_qpootaTjKHVjKccABKsTO21Q@mail.gmail.com>
Message-ID: <CADGJaX9QSBtjEpAr_xFZCNsh55-_7nmRBCXDSNWHaHomN9QxjQ@mail.gmail.com>

Hi all,

As announced, we've released CR 3 of the Spec, API, TCK and the RI and I've
submitted everything to the JCP for the Final Approval Ballot last night:


http://beanvalidation.org/news/2017/07/12/bean-validation-2-0-cr3-submitted-to-final-approval-ballot/

Besides the getLeafBean() clarification, one more change came up which was
to make the order of the <constraint> and <container-element-type> elements
consistent across the XSD for XML constraint mapping files.

The FAB should begin next Tuesday and will run for two weeks. Depending on
the feedback we'll receive from the EC during the voting period, the Final
release will be done shortly thereafter and should ideally be a re-tagged
release of the CR3 versions essentially.

In other words, we are almost there and BV 2.0 will be a finalized spec
hopefully very soon.

Thanks a lot to everyone for your contributions and support!

Cheers,

--Gunnar




2017-07-11 9:02 GMT+02:00 Marco Molteni <moltenma at gmail.com>:

> Ok :)
> Thanks Gunnar and Guillaume!
>
> On Mon, Jul 10, 2017 at 3:25 PM, Gunnar Morling <gunnar at hibernate.org>
> wrote:
>
>> Hi all,
>>
>> As discussed I'm going to submit the BV 2.0 spec to the JCP for Final
>> Approval Ballot tomorrow.
>>
>> Since last week's CR 2, there's one issue that has popped up: BVAL-690
>> [1] which was to clarify the behaviour of
>> ConstraintViolation#getLeafBean() for container element constraints.
>> The change for this is at [2].
>>
>> If nothing else comes up and I don't hear any objections, I'll submit
>> the spec tomorrow.
>>
>> Thanks,
>>
>> --Gunnar
>>
>> [1] https://hibernate.atlassian.net/browse/BVAL-690
>> [2] https://github.com/beanvalidation/beanvalidation-spec/pull/237
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>
>
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20170712/6bef2f57/attachment.html 

From gunnar at hibernate.org  Thu Jul 20 00:38:03 2017
From: gunnar at hibernate.org (Gunnar Morling)
Date: Thu, 20 Jul 2017 07:38:03 +0300
Subject: [bv-dev] Final Approval Ballot has started
Message-ID: <CADGJaX_UgAU=-rEMWSu=b_6HYspG9NKe2MV7TrRiromwi5RUCA@mail.gmail.com>

Hi all,

The Final Approval Ballot for the Bean Validation 2.0 JSR has started and
runs until July 31st. So if you or your company are on the EC, please cast
your vote :)

Also a big thanks to the person who nominated me as "Outstanding spec lead"
for this year's JCP awards; that's appreciated very much! I see it as a
nomination of our entire group really, it has been a great honour and
pleasure to work together with all of you to make BV 2.0 happen!

Cheers,

--Gunnar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20170720/85a2406b/attachment-0001.html