> On 3 Dec 2021, at 15:33, Alan Bateman wrote:
>
> On 03/12/2021 13:39, Michał Kłeczek wrote:
>> Am I missing something?
>>
> I think you understand it correctly. The notion of multi-parent configuration
> and layers is something that was added for those that were focused on interop
> with o
> On 3 Dec 2021, at 14:39, Michał Kłeczek wrote:
>
>
> 2. Is there a way to handle it today?
> (Ab)using transitive dependencies might work - I could introduce artificial
> module M ---(transitive)-->Y2 and make Z require M (so that resolution would
> replace Y1 found by DFS with Y2 required
On 03/12/2021 13:39, Michał Kłeczek wrote:
Am I missing something?
I think you understand it correctly. The notion of multi-parent
configuration and layers is something that was added for those that were
focused on interop with other class loader based systems. It was tracked
as issue #NonHie
Hi All,
During my work on lazy loading of modules I stumbled upon the following
possible dependency graph that I would like to handle:
Y1 X2
^ ^
| |
(non-transitive)(non-transitive)
| |
|