You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by David Blevins <da...@visi.com> on 2010/07/20 07:39:23 UTC
Fwd: JCDI and Bean Validation TCKs
If you have any thoughts, post 'em! :)
Begin forwarded message:
> Resent-From: <db...@visi.com>
> From: David Blevins <da...@visi.com>
> Date: July 19, 2010 9:44:53 PM PDT
> To: dev@geronimo.apache.org
> Subject: JCDI and Bean Validation TCKs
> Reply-To: dev@geronimo.apache.org
>
> Currently we have these setup in the private svn where the Java EE TCK porting modules live. The JCDI and Bean Validation TCKs are public Apache licensed, so we could move the porting modules for those two TCKs into our public svn.
>
> The part of my brain that finds esthetic pleasure in filling cabinets likes everything all organized in the one VM, but the part of me that likes to be more public than private thinks it's unnecessarily restrictive to make people sign the Sun/Apache NDA to get access to things not under that restriction. Specifically, everyone in the related communities (OpenWebBeans, OpenEJB) could easily access the public TCKs. Mark and Gurkan fall into that category now. Both are in the process of getting NDAs filled, but we could definitely speed that up by opening the porting code to the public.
>
> We might even be able to work the JCDI and Bean Validation into our larger test suite right in the main build as they only take a moments to run.
>
> Thoughts?
>
> -David
>
>
Re: JCDI and Bean Validation TCKs
Posted by Kevan Miller <ke...@gmail.com>.
FYI
The JCDI, Bean Validation, Stax, and JAXB test harnesses have been moved to public svn in Geronimo -- http://svn.apache.org/viewvc?rev=966421&view=rev
--kevan
Re: Fwd: JCDI and Bean Validation TCKs
Posted by Mark Struberg <st...@yahoo.de>.
Having those parts public is for sure a save bet. Especially since I hope that
Sun/Oracle now further follows this road ;)
LieGrue,
strub
PS: the TCK NDA is on my stack, but this stack is atm flooded with daywork ;)
----- Original Message ----
> From: David Blevins <da...@visi.com>
> To: dev@openwebbeans.apache.org
> Sent: Tue, July 20, 2010 7:39:23 AM
> Subject: Fwd: JCDI and Bean Validation TCKs
>
> If you have any thoughts, post 'em! :)
>
> Begin forwarded message:
>
> > Resent-From: <db...@visi.com>
> > From: David Blevins <da...@visi.com>
> > Date: July 19, 2010 9:44:53 PM PDT
> > To: dev@geronimo.apache.org
> > Subject: JCDI and Bean Validation TCKs
> > Reply-To: dev@geronimo.apache.org
> >
> > Currently we have these setup in the private svn where the Java EE TCK
>porting modules live. The JCDI and Bean Validation TCKs are public Apache
>licensed, so we could move the porting modules for those two TCKs into our
>public svn.
> >
> > The part of my brain that finds esthetic pleasure in filling cabinets likes
>everything all organized in the one VM, but the part of me that likes to be
>more public than private thinks it's unnecessarily restrictive to make people
>sign the Sun/Apache NDA to get access to things not under that restriction.
>Specifically, everyone in the related communities (OpenWebBeans, OpenEJB) could
>easily access the public TCKs. Mark and Gurkan fall into that category now.
>Both are in the process of getting NDAs filled, but we could definitely speed
>that up by opening the porting code to the public.
> >
> > We might even be able to work the JCDI and Bean Validation into our larger
>test suite right in the main build as they only take a moments to run.
> >
> > Thoughts?
> >
> > -David
> >
> >
>
>