I don't think we need to worry about them....testFindZeroImplementations: I've known about this for a while, and I'll fix it in trunk. It's basically a change made that causes the ResolverUtil to pick up the interface itself, so it always gets at least 1 thing back. The test just needs fixing.
testPartialInputFormats: this was fixed in trunk a while back, and again it's an error in the test, not the main code.
testUrlWithParameterMap: I believe this was also fixed in head by using a SortedMap to ensure things came out in a predictable order
Since these are basically all test artifacts, and the branch sees only minimal development, I'm not sure we really need to fix them there. My 2c.
-t On Mar 30, 2007, at 9:29 AM, Ben Gunter wrote:
When I run the tests on the 1.4.x branch, I get the following failures. What should we do about this?
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
