Hi,
Sorry for the late reply, I was out of town for a few days.
In theory, in Java 16 and 17 EqualsVerifier should just work the way you're used to from Java 8. However, as you noted, the JDK team is working on encapsulating things, which makes it harder for EqualsVerifier to do its thing. It can't use reflection anymore to instantiate classes from the java.* packages. So, we have to provide prefab values for these classes. You can do it yourself by adding a .withPrefabValues() call to your EqualsVerifier invocation, but when it concerns Java classes, I consider it a bug if they don't work and I make sure the prefab value is added by default.
If you open an issue on the issue tracker at
https://github.com/jqno/equalsverifier/issues, I can help you further. Please let me know there which class or classes are causing you problems, and post a small class that uses these classes, along with an equals method, that I can use to reproduce the issue.
Regards,
Jan
--
You received this message because you are subscribed to the Google Groups "equalsverifier" group.