You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@directory.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2018/07/04 07:16:56 UTC
Build failed in Jenkins: dir-ldap-api-win #1135
See <https://builds.apache.org/job/dir-ldap-api-win/1135/display/redirect?page=changes>
Changes:
[elecharny] Fixed the surefire pluging version to a version that is 'fast'
------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-3 (Windows) in workspace <https://builds.apache.org/job/dir-ldap-api-win/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://gitbox.apache.org/repos/asf/directory-ldap-api.git # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/directory-ldap-api.git
> git --version # timeout=10
> git fetch --tags --progress https://gitbox.apache.org/repos/asf/directory-ldap-api.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
> git rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
Checking out Revision 31b608578e00b110c68c90fca129037b61c92c84 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 31b608578e00b110c68c90fca129037b61c92c84
Commit message: "Fixed the surefire pluging version to a version that is 'fast'"
> git rev-list --no-walk e05fe649e2da4dcbe3bfb19d1578bc297b28a636 # timeout=10
Parsing POMs
ERROR: Failed to parse POMs
java.io.IOException: remote file operation failed: <https://builds.apache.org/job/dir-ldap-api-win/ws/> at hudson.remoting.Channel@1ccb8e5d:JNLP4-connect connection from 37.48.69.226/37.48.69.226:62301: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM F:\jenkins\jenkins-slave\workspace\dir-ldap-api-win\integ-osgi\pom.xml: in comment after two dashes (--) next character must be > not - (position: END_TAG seen ...</artifactId>\r\n <!-- ---... @165:17) @ line 165, column 17
at hudson.FilePath.act(FilePath.java:1043)
at hudson.FilePath.act(FilePath.java:1025)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:986)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1794)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM F:\jenkins\jenkins-slave\workspace\dir-ldap-api-win\integ-osgi\pom.xml: in comment after two dashes (--) next character must be > not - (position: END_TAG seen ...</artifactId>\r\n <!-- ---... @165:17) @ line 165, column 17
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1391)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1125)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2918)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:94)
at java.lang.Thread.run(Unknown Source)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 37.48.69.226/37.48.69.226:62301
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)
at hudson.remoting.Channel.call(Channel.java:955)
at hudson.FilePath.act(FilePath.java:1036)
at hudson.FilePath.act(FilePath.java:1025)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:986)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1794)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM F:\jenkins\jenkins-slave\workspace\dir-ldap-api-win\integ-osgi\pom.xml: in comment after two dashes (--) next character must be > not - (position: END_TAG seen ...</artifactId>\r\n <!-- ---... @165:17) @ line 165, column 17
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1328)
... 11 more