hamcrest
Hamcrest 4.0 Draft
This PR represents a potential Hamcrest 4.0 release. It is based on Java 17 as a base. Project dependencies that have been upgraded to the latest versions and has PRs that have been submitted to the Java Hamcrest project.
It is currently a draft PR. I will continue to add as many existing PR submissions to it as I can, starting with the most recent PRs and working my way backwards to older PRs. I will review each PR before adding it and may make some adjustments I think are necessary and/or desirable.
My intent it to make it easy for one of the project maintainers to merge this PR into the master branch rather than have to spend the time updating and merging the individual PRs one at a time (i.e. I will spend the time performing that work into this PR so that a maintainer does not have to).
I am hoping that this will kickstart the Hamcrest 4.0 release process. I would like to see this project continue.
Ok, I think this is ready to be reviewed and merged.
It contains merged code from the following PRs: #442 #441 #439 #433 #431 #430 #429 #404 #383 #381 #379 #345
@tumbarumba - I just noticed that there's section under docs/javadocs with the JavaDocs. I take it this gets generated manually and then checked in for a new release. Should I do that and include it in this PR?
Are there other "release" activities that I can do as part of this PR that would take some of the load off of your plate?
My goal for this PR would be to perform as many tasks as I can (as a contributor) so that it minimizes the amount you (as a maintainer) have to do to get the release out.
@tumbarumba I have figured out the JavaDocs and will commit an updated version. I have some Javadoc comment cleanup to do as part of that process. It may take a day or two...
@tumbarumba OK, I have updated the JavaDocs.
Are there other "release" activities that I can do as part of this PR that would take some of the load off of your plate?
My goal for this PR would be to perform as many tasks as I can (as a contributor) so that it minimizes the amount you (as a maintainer) have to do to get the release out.