TCK for BeanValidation is located here:

http://anonsvn.jboss.org/repos/hibernate/beanvalidation/tck/trunk/

and it is licensed under Apache2, see:
http://twitter.com/emmanuelbernard/status/11750039600

Greetings,
Matthias

On Wed, Apr 7, 2010 at 10:08 AM, Matthias Wessendorf <[email protected]> wrote:
> Hello Kevan,
>
> isn't the TCK for this "free" ? I think JBoss does that nowadays for
> their "new" stuff.
>
> For instance, on OpenWebBeans we use this one:
> http://repository.jboss.com/maven2/org/jboss/jsr299/tck/
>
> -Matthias
>
> On Tue, Apr 6, 2010 at 6:12 PM, Kevan Miller <[email protected]> wrote:
>> FYI,
>> Some information about Apache's participation in the JCP -- 
>> http://apache.org/jcp/
>>
>> Here's general information about getting access to TCK materials --  
>> http://apache.org/jcp/#gettingtck
>>
>> You'd need to fill out the ASF Non-Disclosure Agreement -- 
>> http://apache.org/jcp/ApacheNDA.pdf
>>
>> You can then request access to Sun TCK materials by sending a note to 
>> [email protected].
>>
>> Some projects manage TCK materials within the project (e.g. Geronimo). This 
>> isn't a requirement. For technology projects like BeanValidation with 
>> relatively small TCKs, a committer can send a note to [email protected] 
>> (after they've submitted their NDA) and request the TCK materials. 
>> Typically, the TCK is placed in your home directory on people.apache.org.
>>
>> You are expected to keep TCK materials private. Also, some care needs to be 
>> taken in publicly discussing the TCK. Which is the point that Donald raised 
>> in BVAL-16. I think this restriction only applies to materials obtained 
>> under the NDA. IIUC, this is not the case for the TCK tests currently being 
>> run.
>>
>> --kevan
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Reply via email to