On 5 December 2015 at 11:43, Alan Bateman <[email protected]> wrote: > The boot class path is essentially gone. All the types in the platform and > JDK modules are in named modules. The only way to have types in the unnamed > module of the boot loader is -Xbootclasspath/a or JVM TI > AddToBootstrapClassLoaderSearch. Are you looking to patch your own agent > classes or concerned that you might be running in environments that use > -Xbootclasspath/a?
In essence, yes -- since I know that our product is often used in a setup where multiple agents are present, thus we sometimes need to patch other agents as well, and they might not be in a module. And a lot of agents add themselves to the bootclasspath, either via manifest, or via the Instrumentation API. /Michael
