Hi,
a Maven plugin of mine has the following dependency:
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-core</artifactId>
<version>3.9.9</version>
<scope>provided</scope>
</dependency>
As you can see. the dependency has scope "provided". Now upon building
the plugin I get the warning below. As fars as I can tell, these are
transitive dependencies of the Maven core. Now, I am wondering how to
get rid of these warnings. The only idea, that comes to mind, would be
to declare all of these as explicit dependencies with scope
"provided". but doesn't sound good.
Are there any better ideas?
Thanks,
Jochen
[WARNING]
Some dependencies of Maven Plugins are expected to be in provided scope.
Please make sure that dependencies listed below declared in POM
have set '<scope>provided</scope>' as well.
The following dependencies are in wrong scope:
* org.apache.maven:maven-model:jar:3.9.9:compile
* org.apache.maven:maven-settings:jar:3.9.9:compile
* org.apache.maven:maven-settings-builder:jar:3.9.9:compile
* org.apache.maven:maven-builder-support:jar:3.9.9:compile
* org.apache.maven:maven-repository-metadata:jar:3.9.9:compile
* org.apache.maven:maven-artifact:jar:3.9.9:compile
* org.apache.maven:maven-model-builder:jar:3.9.9:compile
* org.apache.maven:maven-resolver-provider:jar:3.9.9:compile
* org.apache.maven:maven-compat:jar:3.9.9:compile
--
The woman was born in a full-blown thunderstorm. She probably told it
to be quiet. It probably did. (Robert Jordan, Winter's heart)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
