[java-sig-commits] [Bug 736735] Update hamcrest to 1.2 or later
bugzilla at redhat.com
bugzilla at redhat.com
Tue Nov 22 14:58:43 UTC 2011
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=736735
Tomas Radej <tradej at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |tradej at redhat.com
AssignedTo|dwalluck at redhat.com |tradej at redhat.com
--- Comment #1 from Tomas Radej <tradej at redhat.com> 2011-11-22 09:58:42 EST ---
Hi,
Updating Hamcrest is a problem because some depending packages (at least JUnit
at this time) fail to build. The reason is that in 1.2, Hamcrest changed
signatures of some of its methods from <? extends T> to <? super T>. As the
change was intentional, I am talking with JUnit upstream on how to update their
package. If I don't get an answer, we will probably have to make 2 separate
packages for Hamcrest - one for 1.1 and one for 1.2+.
Stay tuned.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the java-sig-commits
mailing list