[bv-dev] ValueExtractionUnwrappingTest: quibble between spec and TCK
Matt Benson
mbenson at apache.org
Fri Mar 30 09:00:52 EDT 2018
Can we just make the change in the source of the spec so that it will have
been handled should we do a 2.1 version? Failing that, could this
particular test be somehow marked as optional for an implementation to
pass? I've made the changes to permit it in the Apache implementation in
any case.
Matt
On Fri, Mar 30, 2018, 7:46 AM Guillaume Smet <guillaume.smet at gmail.com>
wrote:
> Hi Matt,
>
> On Fri, Mar 30, 2018 at 1:01 AM, Matt Benson <mbenson at apache.org> wrote:
>
>> The distinction is perhaps subtle, and I agree that the behavior
>> itself is reasonable; it just doesn't precisely agree with the current
>> wording, and I felt I should raise it as an issue.
>>
>
> I remember us having discussions about this and I think the TCK tests are
> the outcome of this discussion.
>
> It looks like we haven't updated the spec though.
>
> Not sure what to do about this one. The TCK tests make more sense than the
> spec and IIRC that's what we decided to do.
>
> --
> Guillaume
> _______________________________________________
> 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/20180330/738c5780/attachment.html
More information about the beanvalidation-dev
mailing list