On Sun, Oct 4, 2015 at 10:13 AM, Alan Bateman
wrote:
>
> The module system isn't suggesting any solutions, it is instead leaving
> this problem to the build tools and containers.
>
>
Then let me rephrase the question :) The current practice for build tools
to solve the
... Alternatively, instead of defining a new file format, is it possible
for a Java agent to set up layers with the reflective API before the
application starts?
In either case, the build tool could generate the layers file/agent.
Ron
Ron Pressler
paralleluniverse.co
@puniverseco <ht
On Fri, Jul 24, 2015 at 2:22 PM, Alan Bateman alan.bate...@oracle.com
wrote:
On 24/07/2015 10:12, Ron Pressler wrote:
OK, but assuming I have no control over the user's runtime image, am I
correct that programmatically starting the local JMX agent as I do now
(without the Attach API
Hi.
I need to start a local JMX agent on the current JVM and obtain its secret
address; I cannot rely on tools.jar being present so I can't use the attach
mechanism. Currently, I do this with sun.management.Agent.agentmain
and sun.misc.VMSupport.getAgentProperties because that's the only way to
On Mon, Jul 20, 2015 at 2:18 PM, Alan Bateman alan.bate...@oracle.com
wrote:
The attach API (meaning com.sun.tools.attach) is a JDK-specific/supported
API. It should continue to work as it does now in JDK 9. Even better, there
is a new method named startLocalManagementAgent that starts a local