问题描述
我正在研究的 the project 之一具有以下相关配置:
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<version>3.2.0</version>
<configuration>
<failOnWarning>true</failOnWarning>
</configuration>
<executions>
<execution>
<goals>
<goal>analyze-only</goal>
</goals>
</execution>
</executions>
</plugin>
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>hamcrest</artifactId>
<version>2.2</version>
<!-- not scoped to test -->
</dependency>
在执行 mvn clean verify
(apache-maven-3.6.3,java : 17-ea) 时,构建按预期成功。我现在对属性进行了更改,以替换源和目标发布为:
<maven.compiler.release>17</maven.compiler.release>
和终端上的日志读取
[INFO] --- maven-dependency-plugin:3.2.0:analyze-only (default) @ java-8-matchers ---
[WARNING] Non-test scoped test only dependencies found:
[WARNING] org.hamcrest:hamcrest:jar:2.2:compile
导致失败(因为警告)!为什么/如何在 Java 版本的升级中对依赖项进行不同的处理?有什么办法可以解决这个问题?
如果它可能有帮助,此目标的调试日志如下:
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.2.0,parent: jdk.internal.loader.ClassLoaders$AppClassLoader@579bb367]
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only' with basic configurator -->
[DEBUG] (f) analyzer = default
[DEBUG] (f) baseDir = .../java-8-matchers
[DEBUG] (f) failOnWarning = true
[DEBUG] (f) ignoreNonCompile = false
[DEBUG] (f) ignoreUnusedRuntime = false
[DEBUG] (f) outputDirectory = .../java-8-matchers/target
[DEBUG] (f) outputXML = false
[DEBUG] (f) project = MavenProject: uk.co.probablyfine:java-8-matchers:2.0.0-SNAPSHOT @ .../java-8-matchers/pom.xml
[DEBUG] (f) scriptableFlag = $$%%%
[DEBUG] (f) scriptableOutput = false
[DEBUG] (f) skip = false
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
[WARNING] Non-test scoped test only dependencies found:
[WARNING] org.hamcrest:hamcrest:jar:2.2:compile
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (default) on project java-8-matchers: Dependency problems found -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only (default) on project java-8-matchers: Dependency problems found
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
复制使用:
- Git 结帐 this branch。
- 将 maven 配置为使用 Java-17。
- 将
failOnWarning
属性修改为true
。 - 执行
mvn clean verify
。
解决方法
经过调查,我发现问题出在将 maven-dependency-plugin
从版本 3.1.2 升级到 3.2.0,因为在新版本的插件中添加了用于分析的新属性:testArtifactsWithNonTestScope
您可以比较屏幕截图下面的代码:
3.1.2 版:
我在插件中调试了完整的分析器依赖过程,发现了依赖:
<dependency>
<groupId>org.hamcrest</groupId>
<artifactId>hamcrest</artifactId>
<version>2.2</version>
</dependency>
传递给 testArtifactsWithNonTestScope
组工件,因为类 org.hamcrest.MatcherAssert
仅用于测试类。当然,这种行为是不正确的,因为 hamcrest
依赖项中的其他类存在于非测试类中 - maven-dependency-plugin
中肯定存在缺陷。
附言
就像我的想法证明一样,您可以通过以下方式更改非测试类之一:
...
import static org.hamcrest.MatcherAssert.assertThat;
import static org.hamcrest.Matchers.is;
...
public final class Java8Matchers {
public static void customAssert(String reason,boolean assertion) {
assertThat(reason,assertion);
}
...
}
如您所见,我在 org.hamcrest.MatcherAssert
中添加了使用 Java8Matchers
的新方法,之后构建过程将成功完成。
综上所述,您可以通过以下方式解决问题:
- 使用插件 3.1.2 支持的最新版本的 java,并且在错误修复之前不要更新插件
- 关闭构建分析器并等待分析器修复
这个问题与Java版本无关,Java 16也失败了,我看来是maven-dependency-plugin被dependabot从3.1.2升级到3.2.0时出现的,降级解决了问题。