-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hamcrest v3.1 #417
Comments
👋 I'm interested in trying out the changes from #422 in a project where the currently released generic constraints are troublesome. How do you feel about a 3.1-rc (or any qualifier) release to get some feedback on the proposed set of changes? FWIW the generic signature changes will be breaking in my project, but I expect them to be trivial to fix. I'm also game for trying 4.0-rc if you're leaning towards releasing #422 in 4.0. |
Thanks @jstewmon! I'll want to avoid publishing a releasing release candidate just yet. I remember I had a breaking change when I was doing |
Well, that was easy. All I needed to do was run @jstewmon the snapshot jars are available at the Maven Central snapshot repository (see https://oss.sonatype.org/content/repositories/snapshots/org/hamcrest/hamcrest/3.1-SNAPSHOT/). I'd really like to hear how it works out for you. |
This issue is for planning and discussion of features and fixes that will go into Hamcrest v3.1
Included:
Runnable
#423Candidates:
Matchers
andCoreMatchers
See also:
The text was updated successfully, but these errors were encountered: