这是indexloc提供的服务,不要输入任何密码
Skip to content

Releases: raphw/byte-buddy

Byte Buddy 0.6.12

10 Jul 12:26

Choose a tag to compare

  • Added API for altering a method's modifiers when intercepting it.
  • Added API for allowing to filter default values when writing annotations.

Byte Buddy 0.6.11

22 Jun 08:29

Choose a tag to compare

  • Added additional ClassFileLocators for locating jar files in folders and jar files.
  • Added explicit check for invalid access of instance fields from static methods in field accessing interceptors.
  • Added the @StubValue and @FieldValue annotations.

Byte Buddy 0.6.9

18 Jun 19:00

Choose a tag to compare

Invalid release: Corrected the resolution of a type's visibility to another type to determine if a method can be legally overridden. Problem was not resolved.

Byte Buddy 0.6.10

18 Jun 19:01

Choose a tag to compare

  • 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

01 Jun 16:14

Choose a tag to compare

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

01 Jun 11:32

Choose a tag to compare

  • 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

28 May 07:20

Choose a tag to compare

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

Byte Buddy 0.6.5

07 May 13:48

Choose a tag to compare

  • Extended public API with convenience methods.

Byte Buddy 0.6.4

06 May 09:46

Choose a tag to compare

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

Byte Buddy 0.6.3

29 Apr 06:35

Choose a tag to compare

  • 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.