Maven Assembly Plugin resolves extensions of dependencies -- is this intentional?
just a quick question, I thought someone may enlighten me...
Noticed, that Maven _resolves_ and _creates extension realms_ for things I
did not opt to at all. Typical example is nexus-staging-maven-plugin, that
maven 3.6.3 resolves at one moment in my build, despite not using it.
So, what and why is maven-assembly-plugin doing this?
use vanilla maven 3.6.3 and run `mvn clean install -X`
You will notice:
- plugin lists 3 dependencies of project (OK), 1 will be filtered out
(junit, test scope) OK
- and then bunch of extensions are being resolved and created and added to
maven (gitexe, gitsite, felix bundle plugin, and so on, up to