On 26/11/2015 10:13, Michael Rasmussen wrote:
Yeah, I should have been more specific -- the issue is when the package
is loaded from the boot loader, for instance when you have an agent that
has itself on the Boot-Class-Path in the manifest.
Thanks for clarifying.
What you are seeing is specific to JAR files added to the (otherwise
does not exist) boot class path via -Xbootclasspath/a or agent
equivalent. It's not a general issue. We've ignored this case in the
current EA builds on the assumption that it should be very rare, we will
probably need to look at it again.
-Alan.
