On Jul 27, 2007, at 11:57 PM, Jukka Zitting wrote:
If my reasoning is correct, I would treat the issue as a test case bug to be fixed in a future release, and not a blocker to 1.3.1.
I don't consider it a blocker. I think it may have existed on 1.3.0 as well, since I remember trying to test it and being unable to vote because of the failure (and not enough time to investigate it). Since nobody else has seen it, I just assume it is a local setup issue with maven. ....Roy
