Right now, when a toolkit (A) depends on another toolkit (B) which depends on a third toolkit (C), A automatically has access to C when the namespace is not explicit. This could cause jar hell issues where A uses a tag name with no namespace, intending to target one dependency, but getting another.
Toolkit dependencies need to be local-only by default, with possibly an option to re-export the dependency.
Right now, when a toolkit (A) depends on another toolkit (B) which depends on a third toolkit (C), A automatically has access to C when the namespace is not explicit. This could cause jar hell issues where A uses a tag name with no namespace, intending to target one dependency, but getting another. Toolkit dependencies need to be local-only by default, with possibly an option to re-export the dependency.