Bump easymock from 3.6 to 4.2

[dependabot[bot]]

Bumps easymock from 3.6 to 4.2.

Release notes

Sourced from easymock's releases.

4.2

Add support to Java 15. TestSubject is now initialized when null by calling the no-arg constructor.

Change log

• Support OpenJDK 15-EA and class version 59 (#252)
• Try instantiating TestSubject automatically using its constructor without arguments (#251)

4.1

Add support to Java 13 and JUnit 5.

Change log

• Upgrade to Objenesis 3.1 (#250)
• java.lang.IllegalArgumentException: Unsupported class file major version 57/58 (#249)
• Please comply with ASM license when re-distributing ASM (#247)
• Add EasyMockExtension class for JUnit 5 compatibility (#246)
• JUnit 5 support (extension instead of EasyMockRunner) (#245)
• Add getCurrentArgument to get type inference for the returned type (#243)
• CglibTest fails on OpenJDK 13 EA. (#241)

4.0.2

This is a quick fix to remove the second generic parameter that was introduced in version 4. It breaks backward compatibility and is actually unnecessary.

Change log

• No need to have two generic parameters on EasyMock.createMock (#237)

4.0.1

This is a patch release with the sole purpose of moving ASM and CGLIB to their final version with full Java 11 support.

Change log

• Upgrade to cglib 3.2.9 to support Java 11 (#234)
• Upgrade TestNG to version 7 (#233)
• Update to ASM 7.0 for full Java 11 support (#232)

4.0

This release adds support for Java 11 and moves to Java 8.

EasyMock inference has been changed. It should be backward compatible in most cases. However, a type witness might be necessary.

To be clear, starting now List<String> list = mock(List.class); will compile perfectly without any warning. However, String s = mock(List.class); will also compile. But I'm expecting you not to be crazy enough to do such thing. It will do a ClassCastException at runtime anyway.

However, you might see your code failing to infer the return type, in that case, use a type witness e.g. foo(EasyMock.<List<String>>mock(List.class) and it will some the problem nicely,

Commits

• 266c646 Move to version 4.2
• 38d7fd2 Explain how to rollback
• db80adf Only one dash needed
• b8350d9 Upgrade checkstyle
• 7c582d3 Explain a bit more how to launch Android
• 3095b82 Upgrade many plugins and dependencies plus add versions where needed to make ...
• de49472 Upgrade JMH to 1.23
• e5c0d74 Test a bit more and improve error messages when instantiating the TestSubject
• de21604 Merge pull request #251 from tiwanari/tiwanari/auto_instantiate_test_subject
• c5b0ebd Use JUnit 4.13 final version
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)