You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 1.0.0.Alpha1 layers must have all pertaining artifacts defined explicitly.
Consider adding an option to allow transitivity during artifact resolution (will work for Maven compatible repositories, not for local repositories (flat, default)). This option could be global (affects all layers) or perhaps activated per layer.
The text was updated successfully, but these errors were encountered:
The log layer brings log4j-api transitively because log4j-core requires it. OK
The foo layer brings it-greeter:1.0.0 (OK) andlogj-api (NOT OK).
The bar layer brings it-greeter:2.0.0 (OK) andlogj-api (NOT OK).
The app layer brings both foo and bar, which bring log4j-api (NOT OK) and their respective greeter modules (BOMB!)
If transitivity is enabled then duplicate entries (found in parent layers) must be purged from the list of JAR paths before creating the current layer. This also means we have to keep track of JAR paths per layer. Currently we only keep track of ModuleLayer to find the parent(s) of a given layer.
aalmiray
added a commit
to aalmiray/layrry
that referenced
this issue
Feb 24, 2021
As of
1.0.0.Alpha1
layers must have all pertaining artifacts defined explicitly.Consider adding an option to allow transitivity during artifact resolution (will work for Maven compatible repositories, not for local repositories (flat, default)). This option could be global (affects all layers) or perhaps activated per layer.
The text was updated successfully, but these errors were encountered: