[MDEP-773] Getting Warning : Non-test scoped test only dependencies found

[jira-importer]

Venkata Ramana Gujja opened MDEP-773 and commented

I am getting below warning even after I have declared the dependency in pom.xml. I am  executing the command mvn dependency:analyze. I am using @Autowired Java class from spring beans in a JUnit test.

[WARNING] Non-test scoped test only dependencies found:
[WARNING] org.springframework:spring-beans:jar:5.3.10:compile

 

I have declared below dependency in pom.xml

<dependency>

<groupId>org.springframework</groupId>

<artifactId>spring-beans</artifactId>

<version>5.3.10</version>

</dependency>

 

I have attached demo maven project.

 

---

Affects: 3.2.0

Attachments:

• demo.zip (76.44 kB)

2 votes, 5 watchers

[jira-importer]

Eric Lilja commented

Just saw the same issue in one of our projects. The module is a test utility that puts junit in scope compile (by default scope test in parent), because it contains classes (in src/main/java) that extend a class (ExternalResource) in the junit.jar. Apart that use of ExternalResource, our classes in src/main/java do not reference anything else in the JUnit jar file

mvn dependency:analyze says:
[WARNING] Non-test scoped test only dependencies found:
[WARNING] junit:junit:jar:4.13.2:compile

Which is an incorrect warning. This is with version 3.2.0, downgrading to 3.1.2 solves the issue

[jira-importer]

Tommy Andersen commented

We have seen that on a project as well, where a dependency was used in both test and compile scope. But wrongfully identified as a test-only dependency. The problem is that earlier versions of the maven dependency plugin does not seem to support Java 17, and since we treat dependency warnings as errors, we are unable to compile with Java 17 until this has been fixed. Is there no property to disable this check?

[jira-importer]

Pierre Viret commented

We have the same problem while trying to upgrade to java 17. Unfortunately it is not even possible to workaround this by disabling this check for some dependencies:  and other similar config properties do not help in this case. The only think  we can do is set the "failOnWarning" property to false for the projects which hit this bug.

[jira-importer]

Elliotte Rusty Harold commented

dupe of MDEP-753