- Deleted deprecated assert(boolean) in favor of assertTrue(boolean) and assertFalse(boolean). To migrate to JUnit 3.8, rename calls to assert(boolean) to call assertTrue(boolean).
- Added assertFalse() to avoid the difficult of reading the assertTrue(! condition).
- Added assertNotSame(Object, Object).
I guess I'm of the mindset that getting the latest version of a library is the best thing to do. Maybe this is naive. I don't see saving users the trouble of 5 mouse clicks to get another jar as that big of a deal. But, it doesn't seem that using 3.7 is that big of a deal either... I was just curious.
Stephen Colebourne wrote:
Probably because 3.7 does all they need. I've no idea what extra I gain by 3.8.1. And if users only have 3.7 then we don't require them to get another jar. Stephen
----- Original Message ----- From: "__matthewHawthorne" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Friday, October 17, 2003 6:40 PM Subject: [all] why junit 3.7 instead of 3.8.1?
The subject pretty much says it all... why do the majority of commons projects depend on junit 3.7 instead of 3.8.1?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
