Java 无法执行目标org.apache.maven.plugins:maven surefire plugin:2.18.1:test

Java 无法执行目标org.apache.maven.plugins:maven surefire plugin:2.18.1:test,java,maven,maven-3,apache-stanbol,Java,Maven,Maven 3,Apache Stanbol,我正在尝试安装stanbol,出现以下错误 Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 附加错误日志 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on project org.apache.st

我正在尝试安装stanbol,出现以下错误

Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
附加错误日志

[INFO] 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on project org.apache.stanbol.entityhub.ldpath: There are test failures. [ERROR]  [ERROR] Please refer to /home/stanbol-trunk/entityhub/ldpath/target/surefire-reports for the individual test results.

[ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on project org.apache.stanbol.entityhub.ldpath: There are test failures.

Please refer to /home/stanbol-trunk/entityhub/ldpath/target/surefire-reports for the individual test results.   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)  at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)  at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)  at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)  at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)  at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)    at java.lang.reflect.Method.invoke(Method.java:606)     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)  at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)  at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to /home/stanbol-trunk/entityhub/ldpath/target/surefire-reports for the individual test results.   at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)  at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:254)   at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:854)    at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:722)     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)  ... 19 more

[ERROR] 

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

[ERROR] 

[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn <goals> -rf :org.apache.stanbol.entityhub.ldpath
[信息]
[错误]无法在项目org.apache.stanbol.entityhub.ldpath上执行目标org.apache.maven.plugins:maven surefire plugin:2.18.1:test(默认测试):存在测试失败。[错误][错误]请参阅/home/stanbol trunk/entityhub/ldpath/target/surefire报告以了解单个测试结果。
[错误]->[Help 1]org.apache.maven.lifecycle.LifecycleeExecutionException:未能执行目标org.apache.maven.plugins:maven surefire plugin:2.18.1:在项目org.apache.stanbol.entityhub.ldpath上进行测试(默认测试):存在测试失败。
请参阅/home/stanbol trunk/entityhub/ldpath/target/surefire报告以了解单独的测试结果。org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)org.apache.maven.lifecycle.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)在org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)在org.apache.maven.lifecycle.internal.builder.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)在org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)在org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)在org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)在org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)在org.apache.maven.cli.MavenCli.MavenCli.main(MavenCli.java:160)在org.apache.apache.MavenCli.MavenCli.MavenCli.MavenCli.main.doMain(MavenCli.javasun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:606)在org.codehaus.plexus.classworlds.launcher.launchenchenhanced(launcher.java:289)在org.codehaus.plexus.classworlds.launcher.launcher.launcher.launcher(launcher.java:229)在org.codehaus.plexus.classworlds.launcher.launcher.main(launcher.java:356)上原因:org.apache.maven.plugin.MojoFailureException:存在测试失败。
请参阅/home/stanbol trunk/entityhub/ldpath/target/surefire报告以了解单个测试结果。org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)org.apache.maven.plugin.surefireflugin.handleSummary(surefireflugin.java:254)org.apache.maven.plugin.surefire.AbstractSurefireMojo.ExecuteAfterPremissionSchecked(AbstractSurefireMojo.java:854)org.apache.maven.plugin.Surefiremojo.execute(AbstractSurefireMojo.java:722)org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)位于org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)…19更多信息
[错误]
[错误]
[错误]有关错误和可能的解决方案的更多信息,请阅读以下文章:[错误][帮助1]http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[错误]
[错误]纠正问题后,可以使用命令恢复生成
[错误]mvn-rf:org.apache.stanbol.entityhub.ldpath

看起来您正在使用的库中有一些测试被破坏了

如果需要测试错误的详细信息,请查看/home/stanbol trunk/entityhub/ldpath/target/surefire报告

如果仍要安装库,可以运行
mvn clean install-DskipTests


希望有帮助!

右键单击project->“以Maven测试方式运行”。这将自动下载缺少的插件。然后,右键单击project->“更新Maven project”,它将删除包含这些配置的错误

1) @配置

2) @ComponentScan

3) @enableauto配置

@EnableAutoConfiguration是此错误的原因。这将尝试根据pom.xml中的依赖项自动配置应用程序

例如,当pom中有spring数据jpa依赖项时,它将通过查看数据源的application.properties文件,尝试向应用程序添加配置。所以您需要添加数据源来解决这个问题


mvn clean install-DskipTests将帮助您跳过测试,直到您解决错误。

您可以在pom.xml中添加这些标记

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.19.1</version>
            <configuration>
                <skipTests>true</skipTests>
            </configuration>
        </plugin>
    </plugins>
</build>

org.apache.maven.plugins
maven surefire插件
2.19.1
真的

如果您在构建maven项目时遇到上述问题。然后请尝试在pom.xml文件中输入以下代码

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.19.1</version>
            </plugin>
        </plugins>
    </build>

org.apache.maven.plugins
maven surefire插件
2.19.1

出现问题的原因可能是surefire插件版本不正确或未下载。

此外,如果更改测试路径,则可能会出现此问题。在这种情况下,无法找到测试,因此无法执行。

Ohhhh为我工作。谢谢你的帖子-DskipTests它会跳过测试吗?如果有的话。我希望这不会对部署造成伤害。对我有用。谢谢!奇怪的是,对我来说,将版本从2.20.1更改为最新的3.0.0-M1确实解决了surefire插件报告崩溃的问题,它似乎与明显的测试失败无关。请有人解释一下原因