Thanks for all the answers.
I understand the reasoning, but am wondering whether support for automatic
modules in jlink could be made an opt-in decision.
I can see how people are solely using the module path (i.e. no class path)
but work with automatic modules for the sake of simplicity. E.g. tha
On 10/12/2016 22:40, Claes Redestad wrote:
The intended behavior is for jlink to operate on any set of modules to
support linking images for other platforms, operating systems etc (the
java.base jmod shipped with any JDK contains a native JVM), so it may
feel more natural to make it explicit al
Hi Gunnar,
On 2016-12-10 22:50, Gunnar Morling wrote:
Hi,
I've been experimenting a bit with the new jlink tool and got two questions:
* I'm passing a directory with automatic modules via --module-path; this
results in
Error: module-info.class not found for xyz module
Is this expected,
- Mail original -
> De: "Gunnar Morling"
> À: "jigsaw-dev"
> Envoyé: Samedi 10 Décembre 2016 22:50:36
> Objet: jlink and automatic modules
> Hi,
>
> I've been experimenting a bit with the new jlink tool and got two questions:
>
> * I'm passing a directory with automatic modules via --m
Right,
i've forgotten the case of split packages.
Rémi
Le 6 mars 2016 10:49:23 CET, Alan Bateman a écrit :
>
>On 05/03/2016 19:50, fo...@univ-mlv.fr wrote:
>> :
>> if there are jars (with no module metadata) in the modulepath and in
>the classpath,
>> what about having everything in the modulep
On 05/03/2016 19:50, fo...@univ-mlv.fr wrote:
:
if there are jars (with no module metadata) in the modulepath and in the
classpath,
what about having everything in the modulepath (module and jars), nothing in
the classpath and use the unamed modules only in scenarios where currently we
use de
- Mail original -
> De: "Alan Bateman"
> À: "Remi Forax"
> Cc: "Sander Mak" , "jigsaw-dev"
>
> Envoyé: Samedi 5 Mars 2016 10:21:49
> Objet: Re: jlink and automatic modules
>
>
> On 05/03/2016 09:00, Remi Forax
On 05/03/2016 09:00, Remi Forax wrote:
IMO, the real question is "should automatic modules see classes from the
classpath" ?
Automatic modules are for bridging to the class path so they have to
read the unnamed module (or more specifically, they read all unnamed
modules).
-Alan.
yé: Vendredi 4 Mars 2016 09:10:58
> Objet: Re: jlink and automatic modules
>
>
>
> On 03/03/2016 16:04, Sander Mak wrote:
> > :
> > Thanks, that explains it.
> >
> > The difference in behavior between the two modulepaths threw me off for a
> >
On 03/03/2016 16:04, Sander Mak wrote:
:
Thanks, that explains it.
The difference in behavior between the two modulepaths threw me off for a bit.
Whether it's the right thing to do almost sounds more like a philosophical
rather than a technical discussion?
Automatic modules are for migratio
> On 03 Mar 2016, at 16:50, Alan Bateman wrote:
>
> There isn't currently any support for automatic modules at link-time. We have
> an issue tracking it [1] but I think requires thinking through whether it's
> the right thing to do.
Thanks, that explains it.
The difference in behavior betwee
On 03/03/2016 15:38, Sander Mak wrote:
I'm experimenting with an application that consists of proper modules (with
module-info), where one module A requires an automatic module Lib. After
creating modular jars for my application modules and running the application
with both the application mod
12 matches
Mail list logo
