Ouch! ;-> I'm stuck in Java 1.4. :-( Client seems to be upgrade
avoidant.
Hamcrest certainly sounds interesting! But 1013 compile errors when I
import its source into a Java 1.4 project. So one could say that it
leverages Java 5 functionality -- quite heavily. ;-> Is there an earlier
version of Hamcrest that does not use Java 5 features? This doesn't sound
very Google-like to me. ;-> Maybe I should look at jMock constraints or
RMock ConstraintFactory Expression objects, or something else in the Java
1.4 space. Unfortunate, because I like the Hamcrest idea of good
self-describing constraints -- especially for arrays.
It might be best for JBehave to be tied to Java 5. JUnit 4 does. And don't
let my project stop you!
----- Original Message -----
From: "Carlos Villela" <[EMAIL PROTECTED]>
Not necessarily true anymore.Hamcrest 1.1 is full of generics goodness
everywhere. Have a look at the TypeSafeMatcher, for instance:
On 24/07/07, Shane Duan <[EMAIL PROTECTED]> wrote:
Does hamcrest supporting generics now? I had an email conversation a
while ago, and did some digging myself. Because hamcrest needs to
support jMock, it cannot support generics.
On 7/24/07, Elizabeth Keogh <[EMAIL PROTECTED]> wrote:
[...]
> The breaking up of matchers is already done; I haven't started
> including
> Hamcrest yet.
>
> I love working with JBehave in Java 5, and would love it even more if
> it
> used, internally, some of the amazingness that Java 5 provides. It
> seems to
> me that our user base is (entirely?) made up of Java 5 users. It would
> make
> the matchers much simpler, too.
>
> Give me the word and I'll shift it over... :)
"Jeff Grigg" <[EMAIL PROTECTED]> wrote on 24/07/2007 02:20:21:
This strikes me as a really good idea: Making the Matcher creation
methods static for Java 5 and external access, and splitting them
into multiple classes. [...]
(I'm currently working towards introducing JBehave as a BDD tool
in several project heavily into JUnit usage. So I want to be able to
use JBehave assertion logic from JUnit tests. [...]
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
