v1.0.8 - Maintenance Release

Improvements

• Filter out Lagom-related ClassLoaders to allow running on single projects on development mode.

v1.0.7 - Maintenance Release

Fix deadlock bug kamon-io/Kamon#827 by upgrading kanela version. Contributed by @SimunKaracic via #112

v1.0.6 - Maintenance Release

Fixes

• Add AbstractQueuedSynchronizer to preinitialize. Contributed by @dpsoft via #106

Other changes

• update ByteBuddy to 1.10.11
• update shadow
• update scalatest

v1.0.5 - Maintenance Release

Fixes

• Ignores the compiler ClassLoaders introduced in SBT 1.3. This allows instrumentation to work properly when using the sbt-kanela-runner plugins with SBT 1.3.

v1.0.4 - Maintenance Release

Fixes

• Pre initialize classes to avoid ClassCircularityError. Contributed by @andreaTP via #91.
• Change the default Log::maxStackTraceElement. Contributed by @dpsoft via #102.

v1.0.3 - Maintenance Release

Fixes

• Use the last instrumentation classpath when searching for Mixin classes. Contributed by @ivantopo via #101.
• Implements lazy when clause. Contributed by @dpsoft via #100.

Other changes

• Update to bytebuddy 1.10.2.
• Enable jdk10|jdk11|jdk12 in travis tests.
• Remove ClassReplacer experimental feature.

v1.0.2 - Maintenance Release

Fixes

• Improved recognition of Scala-related ClassLoaaders. Some users were unable to get Kamon instrumenting their applications because scala-compiler.jar ended up in their production classpath. The criteria to identify a ClassLoader as a Scala-related one is now: less than 6 jars and contains both jline and scala-compiler. Contributed by @ivantopo via #94.
• Do not clear the registry after reloads. This was making it look as if instrumentation modules are not working after a Play application on Development Mode was reloaded. Fixed by @ivantopo via f5b6412.
• Gracefully handle modules without a within setting in their configuration. Some modules like kamon-executors only ship with the instrumentation but do not apply it unless explicitly enabled by other modules by adding to the within configuration. The default value of within was causing problems when reading the configuration which ended up applying instrumentation to almost all matching classes. Fixed by @ivantopo via #95

Minor Release

• Exclude the SBT Scala compiler ClassLoader from instrumentation. by @ivantopo

Release v1.0.0

All changes in 1.0:

• Upgrade to Bytebuddy 1.9.13. by @dpsoft
• Fix Boostrap Injection feature. by @dpsoft
• Introduce ClassFileVersionValidator. by @dpsoft
• Use Bytebuddy OpenedClassReader. by @dpsoft
• Add Bytebuddy 1.9.13 sources. by @dpsoft
• Remove Legacy Bytecode Support. by @dpsoft
• Change expiration in PoolStrategyCache to 1 minute. by @dpsoft
• Introduce @FieldBridge. by @dpsoft
• Revert disable-class-format-changes default to false. by @dpsoft
• Delay mixin and bridge initialization until transformations are applied. by @ivantopo.
• Exclude the SBT plugins classloader from instrumentation. by @ivantopo.
• Unwrap class suppliers on InstrumentationDescription. by @ivantopo
• Remove paramenter name 'default' for method validation. by @dpsoft
• Ignore modules with invalid configuration. by @ivantopo
• Allow specifying exclude patterns on instrumentation modules. by @ivantopo
• Reduce logging output and default settings. by @ivantopo
• Allow reloading and specifying an instrumentation ClassLoader. by @ivantopo
• Log instrumentation errors to ERROR. by @mladens
• Add instance delegates for interceptors. by @mladens
• Remove ExtensionLoader. by @dpsoft
• Add sleep before System.exit. by @dpsoft
• Instrumentation info provider. by @damdev

Release v1.0.0-RC4

• Allow interception of type initializers. by @dpsoft