Releases · raphw/byte-buddy

Fixed stack size adjustment for accessing double-sized primitive access array elements.
Fixed Advice adjustment of local variable index for debugging information (improves Java agent compatibility).
Renamed TypeLocator to PoolStrategy to avoid confusion with the names.
Removed DescriptionStrategys that rely on fallback-description as those do not properly fallback for meta data.
Added FallbackStrategy as a replacement which allows to reattempt a transformation without using loaded type information.

Fixed annotation resolution for Java 9 to exlude the jdk.internal namespace by default.
Do not copy annotations for default constructor strategies but allow configuring annotation strategy.
Added file-system class file locators for modules in Java 9.
Added convenience methods to default location strategies.
Exclude sun.reflect namespace by default from AgentBuilder to avoid error messages.
Fixed resolution of type varibales for transformed methods and fields.
Fixed stack-aware method visitor when encountering exchanging duplication instructions.

Added POOL_LAST_DEFERRED and POOL_LAST_FALLBACK description strategy.
Fixed resolution of bridge methods for diamond inheritance.
Refactored modifier API to only expose named modifier checks for an element that apply to it.
Fixed resolution for type variables for transformed methods.

Fixed bug with handling of legacy byte code instructions in Advice component.
Cleaned up and refactored usage of AccessController. Added privileged handling to AgentBuilder.
Added proper buffering to non-buffered interaction with file streams.
Make ByteBuddy creation more robust by adding a default fallback for unknown VMs.
Improved support for Java 9.

Lazily compute Implementation.Target and Implementation.Context in case of a type inlining to provide correct feature set. Added validation if this constraint is broken.
Make TypePool using an eager TypeDescription more robust towards errors.

Monitor advice code for inconsistent stack heights at return statements to clean the stack during instrumentation to not trigger verifier errors if such atypical but legal code is encountered.
Do not generate handlers for return values if an instrumented method or an advice method only throws exceptions but never returns regularly.

Added tracer for the state of the operand stack for the Advice component to clear the stack upon a return. Without this, if code would return without leaving the stack empty, a verifier error would be thrown. This typically is only a problem when processing code that was produced by other code generation libraries.

Releases: raphw/byte-buddy