Thanks Stephen Connolly, I need to look into scope a bit more to interpret
your answer better, but I get the gist of it and you've unblocked me from
continuing with the tutorial - thank you.
--
View this message in context:
Reading the Sonatype tutorial at
http://books.sonatype.com/mvnex-book/reference/simple-project-sect-simple-core.html
I see this:
Maven also provides for different dependency scopes. The simple project’s
pom.xml contains a single
dependency—junit:junit:jar:3.8.1+—with a scope of
Ok, here is the mindf?ck...
The strict answer to your exact question as worded (not the one you are
trying to ask) is:
yes, each mojo (a.k.a. plugin goal) invoked gets it's own classpath
consisting of the core Maven classpath plus the dependencies of the plugin
that declares the mojo.
But that
