Rafael Winterhalter

I see now what the issue is. The configuration refers to a Maven Coordinate. You would need to create a "test-jar" and then set: test-jar In the plugin-tag. An easier...

Are you still using the *transform-test* goal? It's resolving the test class path: https://github.com/raphw/byte-buddy/blob/master/byte-buddy-maven-plugin/src/main/java/net/bytebuddy/build/maven/ByteBuddyMojo.java#L668

That's a tricky thing because the class loading will actually implicate a visibility here. This cannot be decided during compilation, and might be legal when loading, this is why it...

Indeed, the release failed due to validation errors, however with the list of errors being an empty list. I assume a bug and reattempt.

You can instrument obfuscated code, but your advice classes need to be excluded from obfuscation. The templating mechanism can otherwise no longer use the byte code as a template.

If you open the jar, you can use javap to inspect class files. I suspect you'd get different output for advice with obfuscation active.

The parameter names should not matter, but if the files are altered, the exclusion does not seem to work. I still expect that a full exclusion would do the trick.

Unfortunately, the internal model is not currently strong enough to capture "on the fly changes" made by ASM visitors. Your best option right now would be to add a custom...

This might be the cache that is used? Can you try to use a `PoolStrategy` that uses a no-op cache?

This is a bug in the modifier resolution for new native methods indeed. Very little used feature, it seems. I just fixed this on master. Could you build Byte Buddy...