Class loading breakage: Will not be able to instrument JDK classes about allocation-instrumenter HOT 4 CLOSED

Keep it named java-allocation-instrumenter-3.0.jar. The JAR file contains metadata that makes the loading JVM put it on the bootclasspath, which is required to instrument JDK classes. The metadata has the name of the JAR file.

Alternatively, you can build from scratch and change in pom.xml to be whatever you want it to be.

from allocation-instrumenter.

Looking at this issue again, I don't think it's a good idea to try to simplify the running process by hard coding the bootstrap classpath in the manifest file, because it's assuming the jar file is in the current working directory with a fixed name, which imposes unwritten constraints to the user and it's hard to follow. I would suggest just removing this file from the generated manifest file and update the document to let user specify -Xbootclasspath/a:allocation-instrumenter.jar just like specifying path in the -javaagent flag.

from allocation-instrumenter.

s/removing this file/removing this line/

from allocation-instrumenter.

There is nothing stopping the user from renaming it and adding the bootclasspath flag if they want to do so. This just provides them a way not to do so.

from allocation-instrumenter.