Re: Re: Specifying module paths

2016-01-16 Thread Robert Scholte
nd any API regarding modulepath. Cheers Tibor On Sat, Jan 16, 2016 at 11:08 AM, Robert Scholte wrote: FYI --- Doorgestuurd bericht --- Van: "Jonathan Gibbons" Aan: jigsaw-...@openjdk.java.net Cc: Onderwerp: Re: Specifying module paths Datum: Sat, 16 Jan 2016 00:22:30 +0

Re: Re: Specifying module paths

2016-01-16 Thread Tibor Digana
ibbons" > Aan: jigsaw-...@openjdk.java.net > Cc: > Onderwerp: Re: Specifying module paths > Datum: Sat, 16 Jan 2016 00:22:30 +0100 > > Winding up this discussion ... > > While the use of a properties file to provide a mapping from module name > to file system artifact ha

Fwd: Re: Specifying module paths

2016-01-16 Thread Robert Scholte
FYI --- Doorgestuurd bericht --- Van: "Jonathan Gibbons" Aan: jigsaw-...@openjdk.java.net Cc: Onderwerp: Re: Specifying module paths Datum: Sat, 16 Jan 2016 00:22:30 +0100 Winding up this discussion ... While the use of a properties file to provide a mapping from module na

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 Tibor Digana
Ask the Oracle :) The classloader must validate the modulepath tree before loading the class files. WDYT? On Fri, Jan 15, 2016 at 10:06 AM, Robert Scholte wrote: > Op Thu, 14 Jan 2016 23:45:32 +0100 schreef Jonathan Gibbons < > jonathan.gibb...@oracle.com>: > > >> >> On 01/14/2016 12:25 PM, e...

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

Re: Specifying module paths

2016-01-14 Thread ecki
Cc: Maven Developers List Sent: Do., 14 Jan. 2016 21:14 Subject: Re: Specifying module paths Hi, on the maven-dev list I've received a couple of responses. The following comments are worth mentioning: Igor Fedorenko says: "This is a very good proposal. My only suggestion is

Re: Specifying module paths

2016-01-14 Thread Robert Scholte
Hi, on the maven-dev list I've received a couple of responses. The following comments are worth mentioning: Igor Fedorenko says: "This is a very good proposal. My only suggestion is to extend javax.tools CompilationTask API to take modulepath map as in-memory parameter. Not a big deal, but i

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-09 Thread Igor Fedorenko
Igor On Fri, Jan 8, 2016, at 12:42 PM, Robert Scholte wrote: > FYI, a new idea to solve our modulepath issue. > Any feedback is appreciated. > > thanks, > Robert > > Forwarded Message ---- > Subject: > Specifying module paths > Date: > Thu, 07 Jan

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-09 Thread Robert Scholte
; thanks, > > Robert > > > > Op Fri, 08 Jan 2016 20:14:33 +0100 schreef Paul Benedict < > > pbened...@apache.org>: > > > > > > It sounds like Maven will have to generate many .properties file in a > >> build. > >> 1) Modules

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-09 Thread Tibor Digana
> > > > thanks, > > > Robert > > > > > > Op Fri, 08 Jan 2016 20:14:33 +0100 schreef Paul Benedict < > > > pbened...@apache.org>: > > > > > > > > > It sounds like Maven will have to generate many .properties file in a > > >> build. &

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-09 Thread Paul Benedict
0:14:33 +0100 schreef Paul Benedict < > > pbened...@apache.org>: > > > > > > It sounds like Maven will have to generate many .properties file in a > >> build. > >> 1) Modules to compile main source > >> 2) Modules to compile test source > &

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-09 Thread Tibor Digana
uild. >> 1) Modules to compile main source >> 2) Modules to compile test source >> 3) Modules to execute tests >> 4) And what about forking? >> >> I am concerned #4 is going to create issues unless the .properties file >> name is unique enough. Perhaps it can

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-09 Thread Robert Scholte
new idea to solve our modulepath issue. Any feedback is appreciated. thanks, Robert ---- Forwarded Message Subject: Specifying module paths Date: Thu, 07 Jan 2016 15:39:43 -0800 From: Jonathan Gibbons To: jigsaw-dev This is a follow-up to some of the recent email discussions r

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-08 Thread Paul Benedict
. Perhaps it can be based on process id. Cheers, Paul On Fri, Jan 8, 2016 at 11:42 AM, Robert Scholte wrote: > FYI, a new idea to solve our modulepath issue. > Any feedback is appreciated. > > thanks, > Robert > > Forwarded Message ---- Subject: Specifying module

[Jigsaw] Fwd: Specifying module paths

2016-01-08 Thread Robert Scholte
FYI, a new idea to solve our modulepath issue. Any feedback is appreciated. thanks, Robert Forwarded Message Subject:Specifying module paths Date: Thu, 07 Jan 2016 15:39:43 -0800 From: Jonathan Gibbons To: jigsaw-dev This is a follow-up to some of the recent