The javadoc cleanup change in 21a0529 also added a few private constructors, including to CoreMatchers:
|
public class CoreMatchers { |
|
|
|
private CoreMatchers() { |
|
} |
This is a breaking change, I found at least one case of a classes extending CoreMatchers:
https://github.com/chromium/chromium/blob/52e4ac4401a6477a9737681e27c6d01ff3ca789f/base/test/android/javatests/src/org/chromium/base/test/util/Matchers.java#L17
Was this deliberate? It isn't obviously related to the other javadoc changes in that commit. If it is deliberate, it could be worth mentioning separately in the release note for the next release.
The javadoc cleanup change in 21a0529 also added a few private constructors, including to
CoreMatchers:JavaHamcrest/hamcrest/src/main/java/org/hamcrest/CoreMatchers.java
Lines 14 to 17 in 21a0529
This is a breaking change, I found at least one case of a classes extending
CoreMatchers:https://github.com/chromium/chromium/blob/52e4ac4401a6477a9737681e27c6d01ff3ca789f/base/test/android/javatests/src/org/chromium/base/test/util/Matchers.java#L17
Was this deliberate? It isn't obviously related to the other javadoc changes in that commit. If it is deliberate, it could be worth mentioning separately in the release note for the next release.