Byte Buddy 0.6.10

• Corrected the resolution of a type's visibility to another type to determine if a method can be legally overridden.

Byte Buddy 0.6.8

Corrected incorrect deployment of version 0.6.7 which does not use a dependency reduced POM for the byte-buddy module.

Byte Buddy 0.6.7

• Upgraded ASM dependency to 5.0.4.
• Fixed OSGi headers in all relevant artifacts.

Warning: The byte-buddy artifact is accidentally deployed with a defect POM file which does not exclude the shaded resources.

Byte Buddy 0.6.6

• Fixed error in resolution of the TargetType pseudo-variable when used as component type of an array.

Byte Buddy 0.6.5

• Extended public API with convenience methods.

Byte Buddy 0.6.4

• Extended public API to accept more general argument types when appropriate.
• Extended @Origin annotation to allow for accepting modifiers.

Byte Buddy 0.6.3

• Made the TypeDescription.ForLoadedType class loader agnostic. Before, a class that was loaded by multiple class loaders would have been considered inequal what is not true for the byte code level.

Byte Buddy 0.6.2

• Added additional class validation such that it becomes impossible to define members on classes that do not fit the class's structure, i.e. default methods on Java interfaces in version seven.
• Added a default Assigner singleton.

Byte Buddy 0.6.1

• Added AnnotationDescription.Builder to allow easy definition of annotation values without loading any values.
• Added possibility to define enumerations at runtime.
• Added possibility to dynamically read enumerations for the MethodCall and InvokeDynamic implementations.
• Further API clean-up.

Byte Buddy 0.6

• Renamed the Instrumentation interface to Implementation to avoid naming conflicts with Java types.
• Renamed the Field annotation to FieldProxy to avoid naming conflicts with Java types.
• Refactored package structure to make the implementation more readable.
• Added possibility to define annotation default values.
• Avoid creation of an auxiliary placeholder type for method rebasements if it is not required.
• Avoid rebasing of methods if they are not instrumented.
• Reimplemented TypeWriter, MethodRegistry and other supporting infrastructure to make the code simpler.
• Refactored testing that is related to the previous infrastructure.