You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by __matthewHawthorne <ma...@phreaker.net> on 2003/10/17 19:40:44 UTC
[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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] why junit 3.7 instead of 3.8.1?
Posted by __matthewHawthorne <ma...@phreaker.net>.
I usually read the release notes to discover the differences between
versions. There are only a few noticable changes between 3.7 and 3.8.1:
- 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" <ma...@phreaker.net>
> To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
> 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: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] why junit 3.7 instead of 3.8.1?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
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" <ma...@phreaker.net>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org