Re: Reusing module name token `*` in -d

Gregg, javac's new behavior for the output directory is only enabled when javac is compiling one or more modules in multi-module mode, which is signified by using the --module-source-path option. In other words, if (and only if) you are compiling many modules together using

Re: Reusing module name token `*` in -d

I think this is an important detail to consider as well. If -d’s argument will now have an implied subdirectory before the class hierarchy, simple Java applications/deployment tools will break, unless the JVM knows exactly what to do about this. However, think about the case where I am

Re: Reusing module name token `*` in -d

Peter, I concede that a hypothetical new --module-output option might address the problem, but I'm still not convinced there is a problem that needs to be addressed. The use case appears to be a desire to compile together a set of of loosely related projects, each with their own source

Re: Reusing module name token `*` in -d

Hi Peter, thanks for your thoughts. An option --module-output would of course solve the same problem and I have on issue with it - on the contrary, it sounds great. > You now want to extend the meaning of asterisk to -d option, which > implies that the output directory containing package

Re: Reusing module name token `*` in -d

Hi, On 01/27/2017 03:27 PM, Nicolai Parlog wrote: Being able to compile a bunch of modules together, and put the resulting single output directory on the module path would seem to be more convenient and thus more desirable. You make it sound like it's "either or" but that would not be the

Re: Reusing module name token `*` in -d

> Being able to compile a bunch of modules together, and put the > resulting single output directory on the module path would seem to > be more convenient and thus more desirable. You make it sound like it's "either or" but that would not be the case. It would be "either you use the asterisk" or

Re: Reusing module name token `*` in -d

On 1/26/17 6:30 AM, Nicolai Parlog wrote: Hi, I see that this feature is unlikely to be in Java 9 ;) , but I want to give it one last push before conceding: Comparing the two ways of compiling a set of modules ... Compiling modules one at a time (when that is possible) is the smallest

Re: Reusing module name token `*` in -d

Hi, I see that this feature is unlikely to be in Java 9 ;) , but I want to give it one last push before conceding: > Comparing the two ways of compiling a set of modules ... > > Compiling modules one at a time (when that is possible) is the > smallest overall change for both the IDE and

Re: Reusing module name token `*` in -d

Hi! > Now, with modules, that continues to be the case: you can put the > -d output directory on the runtime module path, either as a single > "exploded module" or as a directory of "exploded modules". And you can continue to do so unless you use a new feature. The lack generality is maybe not

Re: Reusing module name token `*` in -d

Stephan, There will be many cases where one project contains one module and for those cases, the single module mode compilation will be sufficient and bears the most similarity to the way people organize their project today. At the other end of the scale, there will be cases where a set of

Re: Reusing module name token `*` in -d

- Mail original - > De: "Stephan Herrmann" <stephan.herrm...@berlin.de> > À: jigsaw-dev@openjdk.java.net > Envoyé: Mercredi 25 Janvier 2017 21:05:21 > Objet: Re: Reusing module name token `*` in -d > I found the general direction of this proposal interes

Re: Reusing module name token `*` in -d

I found the general direction of this proposal interesting, but from the reluctance to accept this, I start to think, that maybe the role of multi-module compilation was overrated? I assume that the majority of source code out there is organized in some structure like Project1 +

Re: Reusing module name token `*` in -d

On 1/25/17 12:20 AM, Nicolai Parlog wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Jonathan, thanks for considering this. If nothing else, it would require all the module-specific output directories to be created ahead of time, so that javac can determine which ones to use

Re: Reusing module name token `*` in -d

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Jonathan, thanks for considering this. > If nothing else, it would require all the module-specific output > directories to be created ahead of time, so that javac can > determine which ones to use Why would that be the case? It is not

Re: Reusing module name token `*` in -d

Nicolai, I don't think this proposal is a good way to go. If nothing else, it would require all the module-specific output directories to be created ahead of time, so that javac can determine which ones to use, which would require additional setup commands to be executed after a "make clean" or

Re: Reusing module name token `*` in -d

varargs Warn about potentially unsafe vararg methods none Disable all warnings Rémi - Mail original - De: "Stephan Herrmann" <stephan.herrm...@berlin.de> À: jigsaw-dev@openjdk.java.net Envoyé: Dimanche 22 Janvier 2017 15:25:57 Obj

Re: Reusing module name token `*` in -d

an.herrm...@berlin.de> À: jigsaw-dev@openjdk.java.net Envoyé: Dimanche 22 Janvier 2017 15:25:57 Objet: Re: Reusing module name token `*` in -d On 01/22/2017 02:50 PM, Remi Forax wrote: interesting ! It's now a warning that you can exclude with @SuppressWarnings("module"): src/ma

Re: Reusing module name token `*` in -d

ararg methods none Disable all warnings Rémi - Mail original - De: "Stephan Herrmann" <stephan.herrm...@berlin.de> À: jigsaw-dev@openjdk.java.net Envoyé: Dimanche 22 Janvier 2017 15:25:57 Objet: Re: Reusing module name token `*` in -d On 01/22/2017 02:50

Re: Reusing module name token `*` in -d

Disable all warnings Rémi - Mail original - De: "Stephan Herrmann" <stephan.herrm...@berlin.de> À: jigsaw-dev@openjdk.java.net Envoyé: Dimanche 22 Janvier 2017 15:25:57 Objet: Re: Reusing module name token `*` in -d On 01/22/2017 02:50 PM, Remi Forax wrote:

Re: Reusing module name token `*` in -d

Herrmann" <stephan.herrm...@berlin.de> > À: jigsaw-dev@openjdk.java.net > Envoyé: Dimanche 22 Janvier 2017 15:25:57 > Objet: Re: Reusing module name token `*` in -d > On 01/22/2017 02:50 PM, Remi Forax wrote: >> interesting ! >> >> It's now a warning that you can e

Re: Reusing module name token `*` in -d

inal - De: "Robert Scholte" <rfscho...@apache.org> À: jigsaw-dev@openjdk.java.net Envoyé: Samedi 21 Janvier 2017 20:12:37 Objet: Re: Reusing module name token `*` in -d On Sat, 21 Jan 2017 19:35:28 +0100, Stephan Herrmann <stephan.herrm...@berlin.de> wrote: On 01/21/2017 06

Re: Reusing module name token `*` in -d

;rfscho...@apache.org> > À: jigsaw-dev@openjdk.java.net > Envoyé: Samedi 21 Janvier 2017 20:12:37 > Objet: Re: Reusing module name token `*` in -d > On Sat, 21 Jan 2017 19:35:28 +0100, Stephan Herrmann > <stephan.herrm...@berlin.de> wrote: > >> On 01/21/2017 06:52 PM,

Re: Reusing module name token `*` in -d

On Sat, 21 Jan 2017 19:35:28 +0100, Stephan Herrmann wrote: On 01/21/2017 06:52 PM, fo...@univ-mlv.fr wrote: Robert, How do you compile these 2 modules with Maven ? module foo { exports foo to bar; } module bar { requires foo; } when compiling 'foo' javac

Re: Reusing module name token `*` in -d

On 01/21/2017 06:52 PM, fo...@univ-mlv.fr wrote: Robert, How do you compile these 2 modules with Maven ? module foo { exports foo to bar; } module bar { requires foo; } when compiling 'foo' javac needs to see if 'bar' exists and when compiling 'bar', javac will ask to see 'foo'. I

Re: Reusing module name token `*` in -d

t;Robert Scholte" <rfscho...@apache.org> > À: fo...@univ-mlv.fr, "Nicolai Parlog" <n...@codefx.org> > Cc: jigsaw-dev@openjdk.java.net > Envoyé: Samedi 21 Janvier 2017 17:49:45 > Objet: Re: Reusing module name token `*` in -d > On Sat, 21 Jan 2017 14:55:50 +0100,

Re: Reusing module name token `*` in -d

compatible, this is exactly what was done for the jdk. regards, Rémi - Mail original - De: "Nicolai Parlog" <n...@codefx.org> À: jigsaw-dev@openjdk.java.net Envoyé: Samedi 21 Janvier 2017 11:00:35 Objet: Reusing module name token `*` in -d Hi! Another feature

Re: Reusing module name token `*` in -d

e to read >>> exploded modules, .class in folders, not only modules in jars, >>> so the layout on disk is more or less fixed. >>> >>> My advice is to not try to fight the module layout, it's like >>> trying to fight ocean waves, it's better to surf on it. And yes &

Re: Reusing module name token `*` in -d

- Mail original - > De: "Nicolai Parlog" <n...@codefx.org> > À: fo...@univ-mlv.fr > Cc: jigsaw-dev@openjdk.java.net > Envoyé: Samedi 21 Janvier 2017 13:08:24 > Objet: Re: Reusing module name token `*` in -d > Hi Remi. Hi Nicolai, > >> My advi

Re: Reusing module name token `*` in -d

Rémi > > - Mail original - >> De: "Nicolai Parlog" <n...@codefx.org> À: >> jigsaw-dev@openjdk.java.net Envoyé: Samedi 21 Janvier 2017 >> 11:00:35 Objet: Reusing module name token `*` in -d > >> Hi! >> >> Another feature reques

Re: Reusing module name token `*` in -d

et > Envoyé: Samedi 21 Janvier 2017 11:00:35 > Objet: Reusing module name token `*` in -d > Hi! > > Another feature request from the trenches regarding multi-module > compilation. (It is possible that there was a similar thread a couple of > days/weeks (?) back but I did

Reusing module name token `*` in -d

Hi! Another feature request from the trenches regarding multi-module compilation. (It is possible that there was a similar thread a couple of days/weeks (?) back but I didn't find it.) It would be nice to have the ability to specify module specific target folders, so they do not automatically