3 PM
To: jigsaw-dev@openjdk.java.net
Subject: Re: Avoiding same-package conflicts
On 10/29/2015 05:59 AM, Martin Lehmann wrote:
> Hi all,
>
> I stumbled across the same "issue".
>
>> that having multiple versions of the same library isn't a best practice to
&
Hi all,
I have a question on exporting packages and its handling with derived
classes. Any help appreciated!
In a module mod.x one package "pkgx" is exported containing 2 classes Data
and DataFactory.
Another package "pkgxinternal" is not exported and contains the class
InternalData which is
that the following should compile though (and run too): ((Data)
myDataFactory.createInternalData2()).getName()
Yep, indeed. Compiles and runs.
Thanks again.
Cheers, Martin
From: Peter Levart [mailto:peter.lev...@gmail.com]
Sent: Thursday, August 25, 2016 1:42 PM
To: Martin Lehmann <martin.l
Hi Alan,
thanks for your answers.
Sorry for the late answer but I meanwhile uploaded the example to Github:
https://github.com/accso/java9-jigsaw-examples/tree/master/jigsaw-examples/e
xample_layer-hierarchy
mod.main:
LayerBuilder does the startup of Jigsaw layers:
Hi all,
the new #VersionsInModuleNames seems to be active in JDK9 b136 already.
Switching to b136 breaks the build in one of our examples of our Java9
Jigsaw example suite, cf Github:
https://github.com/accso/java9-jigsaw-examples/tree/master/jigsaw-examples/e
xample_automatic-module-logging
In
Hi all,
I have a follow-up question on the new proposal on #ResourceEncapsulation,
which states:
> The effective package name of a resource named by the string
> `"/foo/bar/baz"`, e.g., is 'foo.bar'.
The idea of using resource paths as "effective package names" definitely
makes sense to me.
Hi Patrick,
you might be interested to have a look at a small tool "depvis" which I wrote
together with a few colleagues.
See https://github.com/accso/java9-jigsaw-depvis
Tested with b144 and GraphViz 2.38.
DepVis does also create GraphViz DOT files for Jigsaw module relationships and
takes