Tags

release 1.6.0:

this adds type checking to non java8 code, but effectively forces all
maven
builds to java 8 only mode.
this is acceptable, because the java agent used already the
multi-release
feature and thus maven builds where already incomplete.
because the boot loader does not support multi release jars the server
and
bootstrap libraries use a simmilar apporach where only the initial
object
creation is done via reflection

release 1.5.1

this release fixes a bug that let the client crash during the connection

release 1.5.0:

the transmit protocol changed drastically without direct backwards
compatibility.
currently the server supports both the new and old protocol.
the client uses the new protocol by default but uses the old protocol
if a system property is set to a specific value.
  the client does not try the other protocol if one fails to connect.

the report protocol does not change, thus files previously exported can
still be read and new files can be read by an old client.

except for the final report to be distinguishable from normal reports
even if the client requested a report.
  the final report is only marked in the transmit protocol, not on disk.
this release does not add any other new features to the protocol.
the other major improvement is that the new protocol allows to easily
add new functionality because the protocol versions are now exchanged
during the greeting.

release 1.4.1

the class hierarchy resolver now can resolve classes using the class
loader resource to avoid class circularity errors

the profiler no longer generates stacks for daemon threads when build
with NO_PROFILE_DAEMONS==true

release 1.4.0:

do the instrumentation in place if the JVM version is 24 or above.
note that this only works if the project was build with java24 and with
multi-release support (maven has no multi-release support!).
this also removes the special support of java 23.

release 1.3.0