Rafael Winterhalter

I created a repo where I tried a POV to see if this is feasible and it seems like a small change which already separates the APIs much more. https://github.com/raphw/apm-agent-java/commit/53e70e0b5f50ada526930962bbbb006a18ba6918

That is not clear to me from the example you provide. Could you try to debug this by `mvnDebug`? You could intercept the method within the stack and see what...

This is merely a consequence of an underlying: java.lang.ClassNotFoundException: org.objectweb.asm.ClassVisitor. Maven swallows this cause. Do not use *byte-buddy-dep* but *byte-buddy*. Then use `ClassVisitorFactory` to bridge between different shading concepts of...

What's your interceptor class, including annotations and imports?

It is, but the static initializer will not be rerun on a retransformation. In this case, you would need to hook before the class is loaded for the first time.

You mean rerun the static initializer? That is not possible, unfortunately, the JVM does not support it.

You are doing it right, but there's nothing that can fix your problem if the initializer already ran.

This is because of the lambda expression. It's compiled to a method of its own which is not visible after inlining. You should avoid lambdas and rather create explicit classes...

By `.load(ClassLoader.getSystemClassLoader(), ClassLoadingStrategy.Default.CHILD_FIRST)` you create a new class in a child loader. Once your regular program loads the class, it won't pick it up from that loader but load the...

Are you running single tests? In this case, it takes longer indeed. The "problem" is that Byte Buddy resolves generics and bridges to correctly proxy types. Even if such type...