没有执行目标org.apache.maven.plugins:maven-surefire插件:2.10:测试。

时间:2022-08-04 17:15:03

I have scoured the internet for almost five days now looking for a fix to this issue, but I cannot seem to find and fix it on my own, mainly because I am so new to both Maven and PlayN so I'm not entirely sure at what I'm looking at exactly. But, it is clearly fizzing up at building the core. Seems it can't download an "artifact filter", and is unable to run Surefire's test. But, I'm just speculating on things I don't quite understand fully, even though I've been trying to research these things like crazy. Any help from more experienced people would be very, very, appreciated. I'm losing my mind on this.

我现在就在互联网上搜索了将近五天寻找解决这一问题,但我似乎无法找到并修复它自己,主要是因为我很新的Maven和PlayN所以我不完全确定我看究竟。但是,很明显,这是在打造核心业务。似乎无法下载“工件过滤器”,无法运行Surefire的测试。但是,我只是在推测一些我不完全理解的东西,尽管我一直在试图研究这些东西,比如疯狂。任何来自经验丰富的人的帮助都会非常、非常、非常感谢。我对这件事已经失去理智了。

[INFO] Building Synthesis Core 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ synthesis-core ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ synthesis-core ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory C:\Users\Josiah\synthesis\core\src\main\resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3:compile (default-compile) @ synthesis-core ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ synthesis-core ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\Josiah\synthesis\core\src\test\resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3:testCompile (default-testCompile) @ synthesis-core ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ synthesis-core ---
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.3/maven-common-artifact-filters-1.3.pom
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Synthesis Metaproject ............................. SUCCESS [1.059s]
[INFO] Synthesis Core .................................... FAILURE [3.538s]
[INFO] Synthesis Java .................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.997s
[INFO] Finished at: Wed Oct 31 23:57:38 EDT 2012
[INFO] Final Memory: 6M/109M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project synthesis-core: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test failed: Plugin org.apache.maven.plugins:maven-surefire-plugin:2.10 or one of its dependencies could not be resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-surefire-plugin:jar:2.10 (): Failed to read artifact descriptor for org.apache.maven.shared:maven-common-artifact-filters:jar:1.3: Could not transfer artifact org.apache.maven.shared:maven-common-artifact-filters:pom:1.3 from/to central (http://repo.maven.apache.org/maven2): Remotely Closed [id: 0x0847a8f3, /192.168.1.54:65153 :> repo.maven.apache.org/93.184.215.223:80] -> [Help 1]

I then had it to print the whole debug logging, and it elaborated a bit on the Surefire bit, displaying all of the Exceptions invoked:

然后,我让它打印整个调试日志,并在Surefire位上进行了详细的阐述,显示了所有被调用的异常:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
10:test (default-test) on project synthesis-core: Execution default-test of goal
 org.apache.maven.plugins:maven-surefire-plugin:2.10:test failed: Plugin org.apa
che.maven.plugins:maven-surefire-plugin:2.10 or one of its dependencies could no
t be resolved: Failed to collect dependencies for org.apache.maven.plugins:maven
-surefire-plugin:jar:2.10 (): Failed to read artifact descriptor for org.apache.
maven.shared:maven-common-artifact-filters:jar:1.3: Could not transfer artifact
org.apache.maven.shared:maven-common-artifact-filters:pom:1.3 from/to central (h
ttp://repo.maven.apache.org/maven2): Connection reset -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on projec
t synthesis-core: Execution default-test of goal org.apache.maven.plugins:maven-
surefire-plugin:2.10:test failed: Plugin org.apache.maven.plugins:maven-surefire
-plugin:2.10 or one of its dependencies could not be resolved: Failed to collect
 dependencies for org.apache.maven.plugins:maven-surefire-plugin:jar:2.10 ()
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:225)
        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.buildProje
ct(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-t
est of goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test failed: Plu
gin org.apache.maven.plugins:maven-surefire-plugin:2.10 or one of its dependenci
es could not be resolved: Failed to collect dependencies for org.apache.maven.pl
ugins:maven-surefire-plugin:jar:2.10 ()
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:82)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
        ... 19 more
Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.
maven.plugins:maven-surefire-plugin:2.10 or one of its dependencies could not be
 resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-sur
efire-plugin:jar:2.10 ()
        at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.re
solve(DefaultPluginDependenciesResolver.java:211)
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.createPlug
inRealm(DefaultMavenPluginManager.java:353)
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.setupPlugi
nRealm(DefaultMavenPluginManager.java:321)
        at org.apache.maven.plugin.DefaultBuildPluginManager.getPluginRealm(Defa
ultBuildPluginManager.java:175)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:78)
        ... 20 more
Caused by: org.sonatype.aether.collection.DependencyCollectionException: Failed
to collect dependencies for org.apache.maven.plugins:maven-surefire-plugin:jar:2
.10 ()
        at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectD
ependencies(DefaultDependencyCollector.java:258)
        at org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDepe
ndencies(DefaultRepositorySystem.java:308)
        at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.re
solve(DefaultPluginDependenciesResolver.java:199)
        ... 24 more
Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to
 read artifact descriptor for org.apache.maven.shared:maven-common-artifact-filt
ers:jar:1.3
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.
loadPom(DefaultArtifactDescriptorReader.java:296)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.
readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
        at org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(
DefaultDependencyCollector.java:412)
        at org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(
DefaultDependencyCollector.java:544)
        at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectD
ependencies(DefaultDependencyCollector.java:240)
        ... 26 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not
 transfer artifact org.apache.maven.shared:maven-common-artifact-filters:pom:1.3
 from/to central (http://repo.maven.apache.org/maven2): Connection reset
        at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def
aultArtifactResolver.java:538)
        at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti
facts(DefaultArtifactResolver.java:216)
        at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti
fact(DefaultArtifactResolver.java:193)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.
loadPom(DefaultArtifactDescriptorReader.java:281)
        ... 30 more
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not tra
nsfer artifact org.apache.maven.shared:maven-common-artifact-filters:pom:1.3 fro
m/to central (http://repo.maven.apache.org/maven2): Connection reset
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(W
agonRepositoryConnector.java:951)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(W
agonRepositoryConnector.java:941)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.
run(WagonRepositoryConnector.java:669)
        at org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(Run
nableErrorForwarder.java:60)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.wagon.TransferFailedException: Connection reset
        at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.fillInput
Data(AbstractHttpClientWagon.java:799)
        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:11
6)
        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
        at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.
run(WagonRepositoryConnector.java:601)
        ... 4 more
Caused by: java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractSess
ionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
        at org.apache.maven.wagon.providers.http.httpclient.impl.io.SocketInputB
uffer.fillBuffer(SocketInputBuffer.java:110)
        at org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractSess
ionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
        at org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultRes
ponseParser.parseHead(DefaultResponseParser.java:98)
        at org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractMess
ageParser.parse(AbstractMessageParser.java:252)
        at org.apache.maven.wagon.providers.http.httpclient.impl.AbstractHttpCli
entConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
        at org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultCli
entConnection.receiveResponseHeader(DefaultClientConnection.java:247)
        at org.apache.maven.wagon.providers.http.httpclient.impl.conn.AbstractCl
ientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
        at org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequest
Executor.doReceiveResponse(HttpRequestExecutor.java:298)
        at org.apache.maven.wagon.providers.http.httpclient.protocol.HttpRequest
Executor.execute(HttpRequestExecutor.java:125)
        at org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultR
equestDirector.tryExecute(DefaultRequestDirector.java:645)
        at org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultR
equestDirector.execute(DefaultRequestDirector.java:464)
        at org.apache.maven.wagon.providers.http.httpclient.impl.client.Abstract
HttpClient.execute(AbstractHttpClient.java:820)
        at org.apache.maven.wagon.providers.http.httpclient.impl.client.Abstract
HttpClient.execute(AbstractHttpClient.java:754)
        at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.execute(A
bstractHttpClientWagon.java:674)
        at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.fillInput
Data(AbstractHttpClientWagon.java:793)
        ... 8 more

EDIT: Adding in my pom.xml for analysis.

编辑:添加我的pom。xml进行分析。

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>com.googlecode.playn</groupId>
    <artifactId>playn-project</artifactId>
    <version>1.3.1</version>
  </parent>

  <groupId>com.hijackedlongboat</groupId>
  <artifactId>synthesis</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>
  <name>Synthesis Metaproject</name>

  <properties>
    <playn.version>1.3.1</playn.version>
  </properties>

  <profiles>
    <profile>
      <id>java</id>
      <activation><activeByDefault>true</activeByDefault></activation>
      <modules><module>java</module></modules>
    </profile>
    <profile>
      <id>android</id>
      <modules><module>android</module></modules>
    </profile>
    <profile>
      <id>ios</id>
      <modules><module>ios</module></modules>
    </profile>
    <profile>
      <id>html</id>
      <modules><module>html</module></modules>
    </profile>
    <profile>
      <id>flash</id>
      <modules><module>flash</module></modules>
    </profile>
  </profiles>

  <modules>
    <module>core</module>
  </modules>
</project>

EDIT 2: RESOLVED Through using the command "mvn dependency::tree" I was able to find a missing repository that wasn't being displayed on the debug and stack trace. The missing repository was "forplay-legacy", which I then added to the pom.xml as follows:

编辑2:通过使用命令“mvn依赖::树”来解析:我能够找到一个丢失的存储库,它没有显示在调试和堆栈跟踪中。丢失的存储库是“forplayinglegacy”,然后我将其添加到pom中。xml,如下所示:

  <repositories>
    <repository>
      <id>forplay-legacy</id>
      <url>http://forplay.googlecode.com/svn/mavenrepo</url>
    </repository>
  </repositories>

10 个解决方案

#1


39  

You're probably missing some dependencies.

您可能缺少一些依赖项。

Locate the dependencies you're missing with mvn dependency::tree, then install them manually, and build your project with the -o (offline) option.

在mvn依赖项中找到缺少的依赖项::树,然后手动安装它们,并使用-o(脱机)选项构建项目。

#2


57  

I had similar issue, I was able to solve it using -U option along with mvn command as

我有类似的问题,我可以使用-U选项和mvn命令解决它。

mvn clean install -U

This worked for me, hope it helps.

这对我很有效,希望能有所帮助。

#3


8  

I had a similar problem but all answers here didn't help me.

我有一个类似的问题,但是所有的答案都没有帮助我。

For me the problem was a failing test. If you are developing in a test driven stlye than a failing / not implemented test shouldn't break the build. I still want my project to build.

对我来说,问题是考试不及格。如果您在测试驱动的stlye中开发,而不是失败/未实现的测试,那么就不应该破坏构建。我仍然希望我的项目能够建立。

To solve this I added a configuration to surefire so that it ignores a failing test.

为了解决这个问题,我给surefire添加了一个配置,这样它就会忽略一个失败的测试。

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

#4


7  

Update the Maven project:

更新Maven项目:

Steps:

步骤:

  1. Right-click on "project"
  2. 右键单击“项目”
  3. Go to "Maven" >> "Update"
  4. 去“Maven”>>“更新”
  5. Wait for all the changes to be applied
  6. 等待应用的所有更改。
  7. Commit the changes (if code is on repo)
  8. 提交更改(如果代码在repo上)
  9. Run
  10. 运行

#5


5  

This error occurs if some unit test cases are failing.

如果某些单元测试用例失败,则会出现此错误。

My error was resolved after changing jdk1.8.0_92 to jdk1.7.0_80.

将jdk1.8.0_92更改为jdk1.7.0_80后,我的错误得到了解决。

In my application, certain unit tests were not compatible with Java 8 so they were failing. The build would succeed with mvn clean install -DskipTests but it is not recommended to skip the unit test.

在我的应用程序中,某些单元测试与Java 8不兼容,因此它们失败了。该构建将通过mvn clean安装-DskipTests获得成功,但不建议跳过单元测试。

#6


1  

I faced the same error, but in my case, the problem was resolved after deleting the /target folder and nbactions.xml file.

我遇到了相同的错误,但是在我的例子中,问题是在删除/target文件夹和nbaction之后解决的。xml文件。

#7


0  

When I encountered the problem, the changes.xml document was malformed (missing an end tag). The fix was to edit the XML to make it well formed.

当我遇到问题时,这些变化。xml文档格式错误(缺少结束标记)。修复程序是编辑XML以使其格式良好。

So checking that the XML is well formed can be important, especially when the release plugin does not complain about it.

因此,检查XML格式是否良好是很重要的,特别是在发布插件没有抱怨的时候。

#8


0  

For me changing the Jenkins version helped.

对我来说,改变Jenkins版本是有帮助的。

  <parent>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>plugin</artifactId>
    <version>1.642.4</version><!-- which version of Jenkins is this plugin built against? -->
  </parent>

#9


0  

Sometimes you get similar sounding errors but for reasons that're really not related to the tools - in this case Surefire plugin.

有时你会听到类似的错误,但原因与工具无关——在这个案例中,Surefire插件。

For me I was getting a similar error but the reason was i wasn't pointing to the correct DB url !

对我来说,我也有类似的错误,但原因是我没有指向正确的DB url !

Among a lot of verbosity (using mvn -X flag) I saw a timeout message.

在大量的冗长(使用mvn -X标志)中,我看到了一个超时消息。

One trick I did was to install IntelliJ on the build server (for debugging purpose) and fixing problems through it first and then uninstalling it and making sure everything works on build server as well.

我的一个诀窍是在构建服务器上安装IntelliJ(用于调试目的),并首先通过它解决问题,然后卸载它,并确保在构建服务器上的所有工作都能正常工作。

#10


0  

I had same issue , i resolved from below steps

我有同样的问题,我从下面的步骤中解决了。

1.->Right click on project->maven->Update project 2.->here i selected "force update for snapshot/release" 3.->After that i compiled again my project and issue got fixed 

#1


39  

You're probably missing some dependencies.

您可能缺少一些依赖项。

Locate the dependencies you're missing with mvn dependency::tree, then install them manually, and build your project with the -o (offline) option.

在mvn依赖项中找到缺少的依赖项::树,然后手动安装它们,并使用-o(脱机)选项构建项目。

#2


57  

I had similar issue, I was able to solve it using -U option along with mvn command as

我有类似的问题,我可以使用-U选项和mvn命令解决它。

mvn clean install -U

This worked for me, hope it helps.

这对我很有效,希望能有所帮助。

#3


8  

I had a similar problem but all answers here didn't help me.

我有一个类似的问题,但是所有的答案都没有帮助我。

For me the problem was a failing test. If you are developing in a test driven stlye than a failing / not implemented test shouldn't break the build. I still want my project to build.

对我来说,问题是考试不及格。如果您在测试驱动的stlye中开发,而不是失败/未实现的测试,那么就不应该破坏构建。我仍然希望我的项目能够建立。

To solve this I added a configuration to surefire so that it ignores a failing test.

为了解决这个问题,我给surefire添加了一个配置,这样它就会忽略一个失败的测试。

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

#4


7  

Update the Maven project:

更新Maven项目:

Steps:

步骤:

  1. Right-click on "project"
  2. 右键单击“项目”
  3. Go to "Maven" >> "Update"
  4. 去“Maven”>>“更新”
  5. Wait for all the changes to be applied
  6. 等待应用的所有更改。
  7. Commit the changes (if code is on repo)
  8. 提交更改(如果代码在repo上)
  9. Run
  10. 运行

#5


5  

This error occurs if some unit test cases are failing.

如果某些单元测试用例失败,则会出现此错误。

My error was resolved after changing jdk1.8.0_92 to jdk1.7.0_80.

将jdk1.8.0_92更改为jdk1.7.0_80后,我的错误得到了解决。

In my application, certain unit tests were not compatible with Java 8 so they were failing. The build would succeed with mvn clean install -DskipTests but it is not recommended to skip the unit test.

在我的应用程序中,某些单元测试与Java 8不兼容,因此它们失败了。该构建将通过mvn clean安装-DskipTests获得成功,但不建议跳过单元测试。

#6


1  

I faced the same error, but in my case, the problem was resolved after deleting the /target folder and nbactions.xml file.

我遇到了相同的错误,但是在我的例子中,问题是在删除/target文件夹和nbaction之后解决的。xml文件。

#7


0  

When I encountered the problem, the changes.xml document was malformed (missing an end tag). The fix was to edit the XML to make it well formed.

当我遇到问题时,这些变化。xml文档格式错误(缺少结束标记)。修复程序是编辑XML以使其格式良好。

So checking that the XML is well formed can be important, especially when the release plugin does not complain about it.

因此,检查XML格式是否良好是很重要的,特别是在发布插件没有抱怨的时候。

#8


0  

For me changing the Jenkins version helped.

对我来说,改变Jenkins版本是有帮助的。

  <parent>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>plugin</artifactId>
    <version>1.642.4</version><!-- which version of Jenkins is this plugin built against? -->
  </parent>

#9


0  

Sometimes you get similar sounding errors but for reasons that're really not related to the tools - in this case Surefire plugin.

有时你会听到类似的错误,但原因与工具无关——在这个案例中,Surefire插件。

For me I was getting a similar error but the reason was i wasn't pointing to the correct DB url !

对我来说,我也有类似的错误,但原因是我没有指向正确的DB url !

Among a lot of verbosity (using mvn -X flag) I saw a timeout message.

在大量的冗长(使用mvn -X标志)中,我看到了一个超时消息。

One trick I did was to install IntelliJ on the build server (for debugging purpose) and fixing problems through it first and then uninstalling it and making sure everything works on build server as well.

我的一个诀窍是在构建服务器上安装IntelliJ(用于调试目的),并首先通过它解决问题,然后卸载它,并确保在构建服务器上的所有工作都能正常工作。

#10


0  

I had same issue , i resolved from below steps

我有同样的问题,我从下面的步骤中解决了。

1.->Right click on project->maven->Update project 2.->here i selected "force update for snapshot/release" 3.->After that i compiled again my project and issue got fixed