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
The name of the scope parameter is a bit misleading since it effectively considers the classpath that is visible for the defined scope. This should be changed as follows:
deprecate the scope parameter and introduce a new parameter classpathScope with the same semantics
create a new scopes (note the s) parameter that allows filtering for real scopes
The text was updated successfully, but these errors were encountered:
- DependencyNode#getScopes() may return an empty set
- DependencyNode#getEffectiveScope() returns "compile" if no scope was defined
- DependencyNodeIdRenderer uses "compile" if no scope was defined
- All NodeNameRenderers need to handle empty scopes by themselfes
Signed-off-by: Stefan Ferstl <st.ferstl@gmail.com>
The name of the
scope
parameter is a bit misleading since it effectively considers the classpath that is visible for the defined scope. This should be changed as follows:scope
parameter and introduce a new parameterclasspathScope
with the same semanticsscopes
(note thes
) parameter that allows filtering for real scopesThe text was updated successfully, but these errors were encountered: