On Mon, Feb 26, 2018 at 5:46 PM Laird Nelson wrote:
> I'm noticing that when I rely on the default DependencySelector installed
> by MavenRepositorySystemUtils#newSession(), which incorporates optionality,
> scope, etc., I still get optional dependencies in my collected results.
>
I meant to inc
Hello:
DependencySelector (
https://maven.apache.org/resolver/apidocs/org/eclipse/aether/collection/DependencySelector.html)
has Javadocs that read (in part): "Decides what dependencies to include in
the dependency graph".
DependencyFilter (
https://maven.apache.org/resolver/apidocs/org/eclipse/a
My guess is, that as soon as a plug-in is resolved (which includes plugin
management) it's prefix is registered. For the default groups the Prefix is
searched in, but that does not apply in this case.
In all cases it can be used, it just has no preferred version or default-cli
configuration in
