On Fri, Apr 10, 2015 at 12:08 PM, Kumar Srinivasan < kumar.x.sriniva...@oracle.com> wrote:
> > On 4/10/2015 11:57 AM, Martin Buchholz wrote: > > > > On Fri, Apr 10, 2015 at 10:33 AM, Kumar Srinivasan < > kumar.x.sriniva...@oracle.com> wrote: >> >> I don't get it. Either providing this information (what "java >> program" is running - main class and/or command line) is generally useful >> or it is not. There's nothing macosx-specific about it. Either provide a >> clean blessed api (i.e. not an environment variable) and have >> >> >> Are you equating environment variable to system property ? >> > > The environment variable is particularly bad because it is just a > private communication mechanism, but one that is even visible to > subprocesses. A proper documented supported public cross-platform API > would be fine, and that would include a system property. > > I now see my jdk9 has a system property > > sun.java.command=<name> > > Why can't AWT use that? > > > It relates to the comment I have below, look at: > > http://hg.openjdk.java.net/jdk9/dev/jdk/file/84c5527f742b/src/java.base/share/native/libjli/java.c#l1412 > I'm confused. Comments in java.c suggest that sun.java.command is not exposed to java land, but my test program clearly tells me it's there! (with jdk9-b57)