hg: jigsaw/jake/jdk: Drop qualified exports to jdk.deploy.osx

2016-01-15 Thread alan . bateman
Changeset: 64d52c3bf9e2 Author:alanb Date: 2016-01-16 07:54 + URL: http://hg.openjdk.java.net/jigsaw/jake/jdk/rev/64d52c3bf9e2 Drop qualified exports to jdk.deploy.osx ! src/java.base/macosx/classes/module-info.java.extra

Re: Specifying module paths

2016-01-15 Thread Jonathan Gibbons
Winding up this discussion ... While the use of a properties file to provide a mapping from module name to file system artifact has some attractive properties, it seems that there is insufficient interest to pursue it further at this time. We can always revisit it later. The same applies to va

hg: jigsaw/jake/langtools: Use jrt-fs forwarding to implement -system(modulepath) when jrt-fs is available on the platform.

2016-01-15 Thread jan . lahoda
Changeset: ac4cbad574a2 Author:jlahoda Date: 2016-01-15 23:41 +0100 URL: http://hg.openjdk.java.net/jigsaw/jake/langtools/rev/ac4cbad574a2 Use jrt-fs forwarding to implement -system(modulepath) when jrt-fs is available on the platform. ! src/jdk.compiler/share/classes/com/sun/tool

Re: RFR: 8068938: Test deploying a XML parser as a module

2016-01-15 Thread huizhe wang
Sorry for the late response! Looks like I need to pay attention to the jigsaw alias from now on :-) On 1/12/2016 12:10 AM, Alan Bateman wrote: On 11/01/2016 03:02, Frank Yuan wrote: Hi Alan and Joe Would you like to have a review for test task https://bugs.openjdk.java.net/browse/JDK-807882

Re: RFR: 8068938: Test deploying a XML parser as a module

2016-01-15 Thread huizhe wang
Sorry for the late response! Looks like I need to pay attention to the jigsaw alias from now on :-) On 1/12/2016 12:10 AM, Alan Bateman wrote: On 11/01/2016 03:02, Frank Yuan wrote: Hi Alan and Joe Would you like to have a review for test task https://bugs.openjdk.java.net/browse/JDK-807882

Re: Specifying module paths

2016-01-15 Thread Robert Scholte
Hi Paul, no, I'm not talking about multiple versions of the same module, that subject is clear to me. Alan described quite precise my issue (it's the first described usecase, although the others are interesting as well). So it seems that if two different modules export the same package, the

Re: Specifying module paths

2016-01-15 Thread Paul Benedict
Robert, in the SOTM document, it explicitly calls out that Module systems are not required to support multiple versions of a module. Correct me if wrong, but I think you're hinting at that? Cheers, Paul On Fri, Jan 15, 2016 at 3:06 AM, Robert Scholte wrote: > Op Thu, 14 Jan 2016 23:45:32 +0100

Re: Specifying module paths

2016-01-15 Thread Alan Bateman
On 15/01/2016 09:06, Robert Scholte wrote: Suppose there's a logging module and a fat module, which also contains the classes of the logging module, but older. In my module-info I have requires logging; requires fat; These modules are in the same directory. Which class is loaded first

Re: Specifying module paths

2016-01-15 Thread Robert Scholte
Op Thu, 14 Jan 2016 23:45:32 +0100 schreef Jonathan Gibbons : On 01/14/2016 12:25 PM, e...@zusammenkunft.net wrote: Hello, If I understood it correctly the modules on the MP must be unique and are not merged, thats why the order inside the directory does not matter for the named module