Sharing experiences with the latest EA build // #ReflectiveAccessToNonExportedTypes #ResourceEncapsulation

[Rafael Winterhalter]

Maybe it depends on the language setup? Mine is German, i.e. all help is
printed in German. Its definitely the right java command.

Am 30.09.2016 5:55 nachm. schrieb "Alan Bateman" <Alan.Bateman at oracle.com>:

> On 30/09/2016 16:16, Rafael Winterhalter wrote:
>
>
>
>> :
>>>
>>> PS: I noticed that when running java (without commands), it still lists
>>> the
>>> non-GNU-style options that are no longer supported.
>>>
>> Can you paste in `java -version` and give an example?
>>
>
> rafael at raftop:~$ ~/jdk-9/bin/java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build 9-ea+138-jigsaw-nightly-h5546-
> 20160929)
> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+138-jigsaw-nightly-h5546-20160929,
> mixed mode)
>
> Running "java" does for example mention:
>
>     -addmods <modulename>[,<modulename>...]
>
> Which was replaced by the GNU-style "--add-modules".
>
> I realize this isn't the meat of the thread but I checked this build and I
> don't see an issue:
>
> $ java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build 9-ea+138-jigsaw-nightly-h5546-
> 20160929)
> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+138-jigsaw-nightly-h5546-20160929,
> mixed mode)
>
> $ java 2>&1 | grep add
>     --add-modules <modulename>[,<modulename>...]
>                   root modules to resolve in addition to the initial
> module.
>
> maybe in "Running java" above it is finding another "java" on the path.
>
> -Alan
>