On Mon, Mar 7, 2016 at 8:58 PM, Alan Bateman <[email protected]> wrote: > > On 07/03/2016 18:23, Volker Simonis wrote: >> >> : >> >> So while the tools are not being refactored, how can we fix the build >> on non-SA platforms if moving the SA dependency to >> module-info.java.extra is no viable solution? I've tried your >> suggestion to add `-addmods ALL-SYSTEM` to the jcmd launchers. It >> seems to work. I still don't see the jdk.hotspot.agent dependency >> displayed by jdeps (is this expected ?), but the resulting tools (i.e. >> jstack) now display all the options, also the ones whoch require the >> SA. > > These tools access SA using core reflection so the jdeps doesn't see the > dependency. Dropping the `requires jdk.htospot.agent and using `-addmods > ALL-SYSTEM` as workaround will resolve it but I'd prefer to avoid this if we > can. > > Erik suggested a build solution to this and may have a patch soon. >
OK, that would be fine. This problem isn't very urgent but it would be good if we could resolve it before the big jake integration into jdk9-dev. Regards, Volker > -Alan.
