You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2020/07/20 16:09:01 UTC
[GitHub] [maven-dependency-plugin] bimargulies-google commented on a change in pull request #80: [MDEP-708] dependency:analyze should recommend test scope where possible
bimargulies-google commented on a change in pull request #80:
URL: https://github.com/apache/maven-dependency-plugin/pull/80#discussion_r457525286
##########
File path: pom.xml
##########
@@ -427,14 +428,18 @@ under the License.
<pomExclude>tree-verbose/pom.xml</pomExclude>
</pomExcludes>
<pomIncludes>
+<!--
Review comment:
Delete it if we no longer want it.
##########
File path: src/main/java/org/apache/maven/plugins/dependency/analyze/AbstractAnalyzeMojo.java
##########
@@ -357,6 +359,15 @@ private boolean checkDependencies()
warning = true;
}
+ if ( !testArtifactsWithNonTestScope.isEmpty() )
+ {
+ getLog().warn( "Non-test scoped test only dependencies found:" );
Review comment:
Is this the message for 'have a broader scope' in the comment above? If so, perhaps change the comment to read more specifically that you are detecting "non-test scoped test-only dependencies'.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org