Hamcrest v3.1

[tumbarumba]

This issue is for planning and discussion of features and fixes that will go into Hamcrest v3.1

Included:

• [x] #419
• [x] #420
• [x] #421
• [x] #422
• [x] #423
• [x] #424

Candidates:

• [ ] Clarify difference between Matchers and CoreMatchers
• [ ] Add JVM compatibility table
• [ ] #416
• [ ] #206
• [ ] #381
• [ ] #403
• [ ] #345

See also:

• #418

[jstewmon]

👋 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.

[tumbarumba]

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 v2.1-rc1, and it broke the CI for a number of downstream projects that were just pulling the latest release, even though it was just a release candidate. However, I'll have a go at releasing a snapshot release (v3.1-SNAPSHOT). Hopefully that will give you a chance to have a play. I'll look at doing that this weekend.

[tumbarumba]

Well, that was easy. All I needed to do was run ./gradlew publishAllPublicationsToMavenRepository.

@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.

[erikmaas-malmberg]

When is the 3.1 version supposed to be released? As it is right now, the 3.0 version was released quite a while back, and there are certain great features already merged.