javac bug when calling javac from the ToolProvider

Hi all, when calling javac from the ToolProvider, i get a NPE with the jdkb152/b153. in getLocationForModule(Path), pathLocations can be null Location getLocationForModule(Path dir) { return pathLocations.get(dir); } getLocationForModule(String) detects that pathLocations may be null an

Re: javac bug when calling javac from the ToolProvider

On 24/01/2017 10:59, Remi Forax wrote: Hi all, when calling javac from the ToolProvider, i get a NPE with the jdkb152/b153. in getLocationForModule(Path), pathLocations can be null Location getLocationForModule(Path dir) { return pathLocations.get(dir); } getLocationForModule(Strin

Re: javac bug when calling javac from the ToolProvider

Thanks Alan, yes, it's the same bug ! i was not able to find it in the database, Rémi - Mail original - > De: "Alan Bateman" > À: "Remi Forax" > Cc: "jigsaw-dev" , "compiler-dev" > > Envoyé: Mardi 24 Janvier 2017 12:08:41 > Objet: Re: javac bug when calling javac from the ToolProvider

hg: jigsaw/jake/jdk: More javadoc cleanup

Changeset: ab671370be6a Author:alanb Date: 2017-01-24 14:52 + URL: http://hg.openjdk.java.net/jigsaw/jake/jdk/rev/ab671370be6a More javadoc cleanup ! src/java.base/share/classes/java/lang/ClassLoader.java ! src/java.base/share/classes/java/lang/module/Configuration.java ! src/j

Re: Review Request: JDK-8173096 jmod files are not world-readable

> On Jan 22, 2017, at 3:17 AM, Peter Levart wrote: > > Hi Mandy, > > On 01/21/2017 03:32 AM, Mandy Chung wrote: >> Updated webrev to put the temporary file in the same containing directory of >> the target file: >> http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8173096/webrev.01 >>

ModuleReferenceImpl has no toString

Hi all, This is a regression introduced in b149 i believe, jdk.internal.module.ModuleReferenceImpl has no toString() which makes the debugging of a configuration harder than it should. I believe the toString() can be added to ModuleReference given this is an abstract class. cheers, Rémi

jdk.unsupported doesn't seems to be available without using --add-modules ?

Hi all, it seems that jdk.unsupported is not among the module available by default. This seems to be a regression. cheers, Rémi

Re: jdk.unsupported doesn't seems to be available without using --add-modules ?

@{@##, my bad, i was using an image generated by jlink instead of the jdk. cheers, Rémi - Mail original - > De: "Remi Forax" > À: "jigsaw-dev" > Envoyé: Mardi 24 Janvier 2017 22:33:44 > Objet: jdk.unsupported doesn't seems to be available without using > --add-modules ? > Hi all, >