Reusing module name token `*` in -d

Remi Forax forax at univ-mlv.fr
Sat Jan 21 10:37:38 UTC 2017


Hi Nicolai,
the runtime (ModuleFinder) is able 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 it means that if you want to modularize an already existing project, you have to change its layout to be jigsaw compatible, this is exactly what was done for the jdk.

regards,
Rémi

----- Mail original -----
> De: "Nicolai Parlog" <nipa at codefx.org>
> À: jigsaw-dev at openjdk.java.net
> 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 didn't find it.)
> 
> It would be nice to have the ability to specify module specific target
> folders, so they do not automatically end up in
> `<whatever-was-given-to-d>/<module-name>`.
> 
> It seems obvious (which could very well make it stupid) to reuse the
> asterisk here and allow something like
> 
> javac
>	--module-path mods
>	--module-source-path "./*/src/main/java"
>	-d "./*/target/classes"
>	-module initial.module
> 
> I have not thought through how this might or might not work with
> multiple module source paths. It looks like the only tractable approach
> would be to not allow more than one -d element.
> 
> so long ... Nicolai
> 
> 
> 
> --
> 
> PGP Key:
>    http://keys.gnupg.net/pks/lookup?op=vindex&search=0xCA3BAD2E9CCCD509
> 
> Web:
>    http://codefx.org
>        a blog about software development
>    https://www.sitepoint.com/java
>        high-quality Java/JVM content
>    http://do-foss.de
>        Free and Open Source Software for the City of Dortmund
> 
> Twitter:
>     https://twitter.com/nipafx


More information about the jigsaw-dev mailing list