Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of kevan.miller@gmail.com
 designates 209.85.213.54 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: Bean Validation TCK version
From: Kevan Miller <kevan.miller@gmail.com>
In-Reply-To: 
 <CAE9L6G3hUjsrh_vV=Jx2K6Yc6eCsUEAXTGuTNixKwNEB-nBSKg@mail.gmail.com>
Date: Mon, 5 Dec 2011 20:22:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC9B3C3A-12A2-442C-867E-4D791BFB3C7A@gmail.com>
References: 
 <CAE9L6G3hUjsrh_vV=Jx2K6Yc6eCsUEAXTGuTNixKwNEB-nBSKg@mail.gmail.com>
To: Geronimo Dev <dev@geronimo.apache.org>

Any geronimo feedback for Matt?

--kevan
On Dec 2, 2011, at 1:20 PM, Matt Benson wrote:

> Hi all; apologies for the cross-post.  For some time in the Apache
> Bean Validation podling we intentionally lagged to the 1.0.3.GA
> version of the Bean Validation TCK because it was our understanding
> that this was the version included in the larger EE TCKs which
> Geronimo, and now TomEE, must satisfy.  This became a real problem
> with the release of version 1.0.5.GA of the TCK, which addressed a bug
> in the original RI *and* TCK so severe that it is literally impossible
> for a given codebase to satisfy the Bean Validation TCK >=3D 1.0.5.GA
> and < 1.0.5.GA simultaneously.  After releasing bval-0.3-incubating,
> we voted for forward progress and made our code compatible with the
> 1.0.5.GA TCK.  Recently I raised the issue on the Bean Validation
> specification development list, and was informed by Emmanuel Bernard
> that the Bean Validation TCK *has* in fact been updated in Java EE, to
> version 1.0.6.GA, which our current trunk also passes. [1]  Now I'd
> like to establish a comfort level among our communities that Geronimo
> and TomEE will be able to use future releases of Apache Bean
> Validation, for when we release 0.4-incubating (or perhaps 1.0, as a
> TLP), your projects will not be able to upgrade the BV implementation
> without also upgrading the corresponding TCK, or (as I am ignorant of
> the procedures wrt the EE TCK) obtaining an updated version of the EE
> TCK which in fact contains the updated BV TCK.
>=20
> Thanks for your attention,
> Matt
>=20
> [1] =
http://lists.jboss.org/pipermail/beanvalidation-dev/2011-December/000103.h=
tml