Jeff Grigg wrote:
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.
Yes - hamcrest requires JDK 1.5+.
It might be best for JBehave to be tied to Java 5. JUnit 4 does. And
don't let my project stop you!
We could have jbehave (optional) extensions for hamcrest that use Java 5 - then
the user would be able to choose.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
