<AWT Dev>  Review Request: 8076264 [macosx] Launching app on MacOSX requires enclosing class
kumar.x.srinivasan at oracle.com
Fri Apr 10 19:08:30 UTC 2015
On 4/10/2015 11:57 AM, Martin Buchholz wrote:
> On Fri, Apr 10, 2015 at 10:33 AM, Kumar Srinivasan
> <kumar.x.srinivasan at oracle.com <mailto:kumar.x.srinivasan at oracle.com>>
>> 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
> Why can't AWT use that?
It relates to the comment I have below, look at:
> (We could improve it by making it "official", i.e. move it to the
> java.* namespace.)
More information about the core-libs-dev