On 14.04.20 20:20, Remi Forax wrote:
Hi Jochen,
JPMS has no notion of of API and implementation of the same jar. It's a concept
of your build tool and not something JPMS knows.
The notion of compilation dependencies and runtime dependencies is not a
concept of JPMS but a concept of your build
Hello everybody,
I try to understand how classloading works when there are multiple child layers
and have a problem.
Let's consider the following situation. There are three layers.
BootLayer (moduleA)
|
|___Child1(moduleB)
|
|__ Child2(modu
Hi Jochen,
JPMS has no notion of of API and implementation of the same jar. It's a concept
of your build tool and not something JPMS knows.
The notion of compilation dependencies and runtime dependencies is not a
concept of JPMS but a concept of your build tools.
In term of JPMS, if you want to
On 4/14/2020 3:12 AM, Jochen Theodorou wrote:
On 14.04.20 11:09, Alan Bateman wrote:
On 14/04/2020 09:24, Jochen Theodorou wrote:
Hi all,
I am wondering if there is a solution purely in the module-info for
this:
* Project requires Library1 and Library2
* SomeLibrary requires SharedApi
* Oth
On 14.04.20 11:09, Alan Bateman wrote:
On 14/04/2020 09:24, Jochen Theodorou wrote:
Hi all,
I am wondering if there is a solution purely in the module-info for this:
* Project requires Library1 and Library2
* SomeLibrary requires SharedApi
* OtherLibrary requires SharedApiImpl
The problem is,
On 14/04/2020 09:24, Jochen Theodorou wrote:
Hi all,
I am wondering if there is a solution purely in the module-info for this:
* Project requires Library1 and Library2
* SomeLibrary requires SharedApi
* OtherLibrary requires SharedApiImpl
The problem is, that it will not compile because Shared
Hi all,
I am wondering if there is a solution purely in the module-info for this:
* Project requires Library1 and Library2
* SomeLibrary requires SharedApi
* OtherLibrary requires SharedApiImpl
The problem is, that it will not compile because SharedApi and
SharedApiImpl implement the same packa
