Burned By Tapestry 4's disable-caching again.

Using my fancy new development desktop (MacPro 8 Core, 8 Gb), I figured I'd save some time by running my Selenium tests in parallel. Tapestry started bombing at random, dumping this nugget to the log file:

Property visitState has already been accounted for by the element at Annotation @org.apache.tapestry.annotations.InjectState(value=visit) of public abstract

This is what happens when you turn on Tapestry 4.0's disable caching flag (-Dorg.apache.tapestry.disable-caching=true). Ugh. I have to turn this flag on for development, and then turn it off for proper testing? Check out http://issues.apache.org/jira/browse/TAPESTRY-846 and its sibling http://issues.apache.org/jira/browse/TAPESTRY-848. Given the comments on these tickets, I don't think I'll spend the time attempting the patch.