See <https://builds.apache.org/job/DeltaSpike%20OWB%201.1.6/860/changes>

Changes:

[tandraschko] DELTASPIKE-1150 Ignore "external" links in CLIENTWINDOW-mode

[gpetracek] DELTASPIKE-1151 dropped optional cleanup

[johndament] DELTASPIKE-1152 Adding support for first and top in method name,

[johndament] DELTASPIKE-1153 Added support for ordering without a where clause.

[johndament] DELTASPIKE-1152 DELTASPIKE-1153 Doc clean up.

[tandraschko] DELTASPIKE-1149 CLIENTWINDOW tokenizedRedirect should ignore 
ctrl-key

[tandraschko] DELTASPIKE-1142 Documentation wrong: an interface does not 
implement

[tandraschko] DELTASPIKE-1154 [perf] use EntityVerifier in a static way

[tandraschko] DELTASPIKE-1155 tableName fallback to Metamodel only when not 
defined on

[tandraschko] DELTASPIKE-1154 remove "unused" verifier API for now

------------------------------------------
Started by upstream project "DeltaSpike for CDI 1.0" build number 23
originally caused by:
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on jenkins-test-b4 (jenkins-cloud-4GB cloud-slave Ubuntu 
ubuntu jenkins-cloud-8GB) in workspace 
<https://builds.apache.org/job/DeltaSpike%20OWB%201.1.6/ws/>
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/deltaspike.git
 > git init <https://builds.apache.org/job/DeltaSpike%20OWB%201.1.6/ws/> # 
 > timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/deltaspike.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/deltaspike.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/deltaspike.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/deltaspike.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/deltaspike.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/deltaspike.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 0bb287f56a3e4d2afc9f731ce56fc03102a7dd08 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0bb287f56a3e4d2afc9f731ce56fc03102a7dd08
 > git rev-list 531f0450defa2e1abbcf1d9db33eb8e403ce2ab6 # timeout=10
Parsing POMs
ERROR: Failed to parse POMs
java.io.IOException: remote file operation failed: 
<https://builds.apache.org/job/DeltaSpike%20OWB%201.1.6/ws/> at 
hudson.remoting.Channel@4103f0e9:jenkins-test-b4: 
hudson.remoting.ProxyException: 
hudson.maven.MavenModuleSetBuild$MavenExecutionException: 
hudson.maven.MavenEmbedderException: 1 problem was encountered while building 
the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected 
character in markup % (position: START_TAG seen ...</username>\n     
<password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

        at hudson.FilePath.act(FilePath.java:986)
        at hudson.FilePath.act(FilePath.java:968)
        at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960)
        at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)
        at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
        at hudson.model.Run.execute(Run.java:1738)
        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
        at hudson.model.ResourceController.execute(ResourceController.java:98)
        at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.remoting.ProxyException: 
hudson.maven.MavenModuleSetBuild$MavenExecutionException: 
hudson.maven.MavenEmbedderException: 1 problem was encountered while building 
the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected 
character in markup % (position: START_TAG seen ...</username>\n     
<password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1362)
        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719)
        at hudson.remoting.UserRequest.perform(UserRequest.java:120)
        at hudson.remoting.UserRequest.perform(UserRequest.java:48)
        at hudson.remoting.Request$2.run(Request.java:326)
        at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
        at ......remote call to jenkins-test-b4(Native Method)
        at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
        at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
        at hudson.remoting.Channel.call(Channel.java:781)
        at hudson.FilePath.act(FilePath.java:979)
        ... 8 more
Caused by: hudson.remoting.ProxyException: hudson.maven.MavenEmbedderException: 
1 problem was encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected 
character in markup % (position: START_TAG seen ...</username>\n     
<password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

        at hudson.maven.MavenEmbedder.<init>(MavenEmbedder.java:128)
        at hudson.maven.MavenEmbedder.<init>(MavenEmbedder.java:109)
        at hudson.maven.MavenEmbedder.<init>(MavenEmbedder.java:136)
        at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:212)
        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1295)
        at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)
        at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719)
        at hudson.remoting.UserRequest.perform(UserRequest.java:120)
        at hudson.remoting.UserRequest.perform(UserRequest.java:48)
        at hudson.remoting.Request$2.run(Request.java:326)
        at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: hudson.remoting.ProxyException: hudson.maven.MavenEmbedderException: 
1 problem was encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected 
character in markup % (position: START_TAG seen ...</username>\n     
<password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

        at hudson.maven.MavenEmbedder.getSettings(MavenEmbedder.java:261)
        at 
hudson.maven.MavenEmbedder.buildMavenExecutionRequest(MavenEmbedder.java:157)
        at hudson.maven.MavenEmbedder.<init>(MavenEmbedder.java:120)
        ... 14 more
Caused by: hudson.remoting.ProxyException: 
org.apache.maven.settings.building.SettingsBuildingException: 1 problem was 
encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected 
character in markup % (position: START_TAG seen ...</username>\n     
<password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

        at 
org.apache.maven.settings.building.DefaultSettingsBuilder.build(DefaultSettingsBuilder.java:116)
        at hudson.maven.MavenEmbedder.getSettings(MavenEmbedder.java:259)
        ... 16 more

Reply via email to