If you want to enforce that kind of consistency - that no two
application modules should export same named package - it should be
possible to implement a user defined jlink plugin to enforce the same.
-Sundar
On 10/13/2016 12:35 AM, Alan Bateman wrote:
> On 12/10/2016 19:17, Karl Heinz Marbaise
On 12/10/2016 19:17, Karl Heinz Marbaise wrote:
Hi,
i have a question concerning the jlink command in JDK 9..(EA +138 build)
I have created two modules lets call them module A and module B
(module-info.java):
module A {
requires java.base;
exports com.single.package;
}
module B {
In general, there is no problem with modules in the image or on the
modulepath that contain and export the same package. The problem comes
when a single module requires two other modules which both contain and
export the same package. There is no such single module in the image
you're creating
Hi,
i have a question concerning the jlink command in JDK 9..(EA +138 build)
I have created two modules lets call them module A and module B
(module-info.java):
module A {
requires java.base;
exports com.single.package;
}
module B {
requires java.base;
exports
