ByteBuddy 1.18.11 doesn't work under Java 26 for EasyMock.

[henri-tremblay]

EasyMock can't mock using ByteBuddy under Java 26 and byte-buddy 1.18.11.

Seems to be due by the way byte-buddy is now now using Unsafe. But I'm not aware of the official transition method to make it work.

See easymock/easymock#908 for details and a reproducer.

[raphw]

You cannot use Unsafe anymore (unless you enable it, and Oracle has not removed it yet) but you need to resolve a MethodHandles.Lookup and pass it to a ClassLoadingStrategy based on this handle. This also requires that you have access to the package from this handle, which can be tricky when it comes to modules. For exported packages and non-modules, it is straight forward, but for the general case there is unfortunately no drop-in replacement. Can you point me to where you are using an injection strategy today?

…

Message ID: ***@***.***>

[raphw]

I see from your stack trace that you are already using a lookup based injector: Caused by: java.lang.IllegalArgumentException: org.apache.shiro.web.filter.PathMatchingFilter$$$EasyMock$2 must be defined in the same package as org.easymock.internal.ClassProxyFactory at net.bytebuddy.dynamic.loading.ClassInjector$UsingLookup.injectRaw(ClassInjector.java:1728) The problem is that the JVM does not accept a package that is different from the one that the lookup is resolved against. You can adjust the lookup object, or change the mock's package to org.easymock.internal from where I assume the lookup is resolved.

…

Message ID: ***@***.***> >

[raphw]

I can see the error here: https://github.com/easymock/easymock/blob/master/core/src/main/java/org/easymock/internal/ClassProxyFactory.java#L265 You would need to call .in(toMock) on the lookup. Note that this will fail if the class is not accessible to the caller class of MethodHandles.lookup(). In such a case, you will need the mock to a package that you can access. You can also attach a Java agent and adjust the module graph, but note that dynamic attachment via ByteBuddyAgent.install() is also limited in modern JVMs.

…

Message ID: ***@***.***> >> >

[henri-tremblay]

More and more fun with integrity by default. Thanks for the answers, I'll dig.