Maven插件单元测试报ComponentLookupException(testing-harness)异常
待解决问题记录
- 已开发完成一款Maven插件,需为其补充单元测试用例。参照Maven官方发布的插件测试指引,选用官方
maven-plugin-testing-harness作为测试基础框架。 - 按指引流程搭建最小测试项目后,程序直接抛出组件查找异常,完整报错栈片段为:
org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException role: org.apache.maven.plugin.Mojo roleHint: org.tbee.xml2xxx:xml2yaml-maven-plugin:0.2.0:convert at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205) at org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:410) at org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:355) at org.tbee.xml2yaml.maven.plugin.XML2YAMLMojoTest.testSomething(XML2YAMLMojoTest.java:52) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at junit.framework.TestCase.runTest(TestCase.java:177) at junit.framework.TestCase.runBare(TestCase.java:142) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:130) at junit.framework.TestSuite.runTest(TestSuite.java:241) at junit.framework.TestSuite.run(TestSuite.java:236) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:542) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:770) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:464) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210) Caused by: java.util.NoSuchElementException at java.base/java.util.Collections$EmptyIterator.next(Collections.java:4210) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263) ... 24 common frames omitted
排查过程记录
- 调试过程中观察到,
DefaultPlexusContainer可以匹配到待测插件的正确GAV坐标,但无法确认容器是否实际完成了待测项目POM文件的加载。 - 尝试切换为基于测试规则的测试方案替代原有的基类继承测试方案:初期遇到
Rule.getTestFile方法不存在的问题,替换为本地普通文件访问逻辑后,程序可以正常加载测试用POM文件,也能从POM中解析推导对应插件的GAV坐标,到这一步所有前置流程均运行正常。 - 执行后续组件查找
lookup方法时,依旧在DefaultPlexusContainer.locate位置抛出和之前完全一致的组件查找异常,新的报错栈片段为:
org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException role: org.apache.maven.plugin.Mojo roleHint: org.tbee.xml2xxx:xml2yaml-maven-plugin:0.2.0:convert at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:205) at org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:410) at org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:355) at org.apache.maven.plugin.testing.MojoRule.lookupMojo(MojoRule.java:164) at org.tbee.xml2yaml.maven.plugin.XML2YAMLMojoTest.testSomething(XML2YAMLMojoTest.java:60) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.apache.maven.plugin.testing.MojoRule$2.evaluate(MojoRule.java:308) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.internal.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:542) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:770) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:464) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210) Caused by: java.util.NoSuchElementException at java.base/java.util.Collections$EmptyIterator.next(Collections.java:4210) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263) ... 33 common frames omitted
待确认疑问
- 该组件查找异常是否和当前使用的Java 11运行环境有关?目前未查询到
maven-plugin-testing-harness明确标注的兼容Java版本上限说明。 - 补充说明:这款Maven插件本身在实际构建流程中运行完全正常,测试流程报错不代表插件存在功能可用性问题。
内容的提问来源于stack exchange,提问作者tbeernot
相关产品推荐
相关产品推荐

