I would say it really belongs in Tapestry-test. It isn't necessary
that Tapestry-test be deprecated if there is an ongoing need for it.
FYI, I believe the discussion that lead to deprecation status was:
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Discussion-Future-of-tapestry-test-amp-friends-td5722648.html
The tapestry-test module can't actually be removed until Tapestry
tests that depend on it are rewritten in Spock and Geb, which could
take years unless somebody wants to make it their full time job for a
while.
Maybe the module should be kept (not deprecated), but only some
classes deprecated?
The long-term future of tapestry-test is still open to discussion as
far as I'm concerned. There are not only Tapestry's own tests, but
Tapestry user's test that depend on tapestry-test, and nobody ever
wants to rewrite tests.
On Tue, Mar 18, 2014 at 5:54 AM, Lance Java <lance.j...@googlemail.com> wrote:
> I'd like to create a JUnit4ClassRunner to simplify integration testing of
> Tapestry IOC services. More details here
> https://issues.apache.org/jira/browse/TAP5-2273
>
> I'm not sure which gradle module the test runner should live in?
> tapestry-test is deprecated and tapestry-internal-test is not intended for
> external use. Any suggestions?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
