Hi Bob, I forgot to mention that I also feel that tapestry-test is a bit
heavy weight.
This junit runner is for testing tapestry-ioc apps. Tapestry-test has
transitive dependencies on tapestry-web, selenium, jetty etc. I'm not sure
people want all that on their classpath when testing an IOC only
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
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:
