Skip to content

Bump classgraph from 4.8.115 to 4.8.128

bornholdt requested to merge dependabot/maven/io.github.classgraph-classgraph-4.8.128 into master

Bumps classgraph from 4.8.115 to 4.8.128.

Release notes

Sourced from classgraph's releases.

classgraph-4.8.128

Optimize reflection by caching fields and methods of introspected classes by name.

classgraph-4.8.127

Fix illegal reflective access warning on stderr in JDK 11 (#579, thanks to @josephlbarnett for reporting).

classgraph-4.8.126

Remove -parameters flag from javac parameters of non-test build, introduced in 4.8.121, because it introduced issues with -Xlint:classfile or -Xlint:all combined with -Werror (#577, thanks to @Stephan202 for reporting)

classgraph-4.8.125

Remove a debugging setting which produced a warning on stderr (#568).

classgraph-4.8.124

Allow circumvention of encapsulation in JDK 16+ via jvm-driver, in addition to existing Narcissus support. Details are on README.md page for ClassGraph GitHub project.

classgraph-4.8.123

More compatibility fixes for IBM Semeru.

classgraph-4.8.122

Add support for ClassGraph.CIRCUMVENT_ENCAPSULATION = true to work on IBM Semeru, an OpenJDK fork (#563).

classgraph-4.8.121

Optimization of reflection code (no functional changes compared to previous release)

classgraph-4.8.120

First version that is fully compatible with JDK 16+

The JDK team decided to switch on strong encapsulation in JDK 16+. That means that ClassGraph cannot find the classpath, if all of the following are true:

  • You are running on JDK 16+
  • You are using a legacy classloader (rather than the module system)
  • The legacy classloader does not expose its classpath via a public field or method
  • The classloader is loaded in a different module from your user code

If your ClassGraph code works in JDK versions less than 16 but breaks in JDK 16+ (meaning that ClassGraph can no longer find your classes), you have probably run into this problem.

You can circumvent this restriction by:

  • Adding the Narcissus library to your project as an extra dependency (only Linux x86/x64, Windows x86/x64, and Mac OS X x64 are currently supported).
  • Setting ClassGraph.CIRCUMVENT_ENCAPSULATION = true; before interacting with ClassGraph in any other way (this will load the Narcissus library as ClassGraph's reflection driver).

This release of ClassGraph uses Narcissus to silently circumvent all of Java's security mechanisms (visibility/access checks, security manager restrictions, and strong encapsulation), in order to read the classpath from private fields and methods of classloaders. Narcissus is a collaboration between:

JDK 16's strong encapsulation is just the first step of trying to lock down Java's internals, so further restrictions are possible (e.g. it is likely that setAccessible(true) will fail in future JDK releases, even within a module, and probably the JNI API will be locked down soon, making Narcissus require a commandline flag to work).

Please convince your upstream runtime environment to expose the full classpath from their classloader using a public method or field, otherwise ClassGraph may stop working for your runtime environment in the future.

... (truncated)

Commits

Merge request reports