Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of nbubna@gmail.com designates
 209.85.212.177 as permitted sender)
MIME-Version: 1.0
Sender: nbubna@gmail.com
In-Reply-To: 
 <CAFyaDjHs-RT29RCoaYK6nCV6r9E2_QSfK6x2J6K8B0wbpHsO1w@mail.gmail.com>
References: 
 <CADL3G_D9ePsmsPqnEMzasXYWgHxasg0rM=8o=O6=mUQzq+7i7w@mail.gmail.com>
	<CAFyaDjHs-RT29RCoaYK6nCV6r9E2_QSfK6x2J6K8B0wbpHsO1w@mail.gmail.com>
Date: Thu, 10 May 2012 09:58:19 -0700
Message-ID: 
 <CAFyaDjEG=6GzWDoxuQh-8_WUUZ6wtAoSjdJSzom0Sic8VhrFiQ@mail.gmail.com>
Subject: Fwd: Does Apache already have access to JSR 223 TCK
From: Nathan Bubna <nbubna@apache.org>
To: dev@commons.apache.org, Velocity Developers List <dev@velocity.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Do ya'll know the answer to this?

---------- Forwarded message ----------
From: Dishara Wijewardana <ddwijewardana@gmail.com>
Date: Thu, May 10, 2012 at 9:50 AM
Subject: Does Apache already have access to JSR 223 TCK
To: Velocity Developers List <dev@velocity.apache.org>, Claude Brisson
<claude@renegat.net>


Hi all,
I saw some mail archives that Apache BSF has requested/had intention for
requesting for the JSR 223 TCK. If they have that from Apache point of
view, I think we can also use that.
It is really helpful when implementing the spec. (specially if the TCK code
is available, it is very efficient in implementing it).


--
Thanks
/Dishara

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org