You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Apache Jenkins Server <hu...@hudson.apache.org> on 2011/04/26 21:14:52 UTC

Build failed in Jenkins: sling-trunk-1.5 #1190

See <https://builds.apache.org/hudson/job/sling-trunk-1.5/1190/changes>

Changes:

[justin] adding this dumb mac file to .gitignore

[justin] adding gitignore for integration tests

[justin] SLING-2057 - wrapping the servlet context / request dispatcher for other contexts to use the original JspFactory when doing forwards or includes on a different context.

------------------------------------------
Started by an SCM change
Building remotely on ubuntu1
Updating http://svn.apache.org/repos/asf/sling/trunk
U         bundles/scripting/jsp/src/main/java/org/apache/sling/scripting/jsp/jasper/runtime/PageContextImpl.java
A         bundles/scripting/jsp/src/main/java/org/apache/sling/scripting/jsp/jasper/runtime/InternalServletConfigWrapper.java
A         bundles/scripting/jsp/src/main/java/org/apache/sling/scripting/jsp/jasper/runtime/ExternalServletContextWrapper.java
U         bundles/scripting/jsp/src/main/java/org/apache/sling/scripting/jsp/jasper/compiler/JspRuntimeContext.java
U         .gitignore
A         testing/samples/integration-tests/.gitignore
At revision 1096852
ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro
Found mavenVersion 2.2.1 from file jar:file:/home/hudson/tools/maven/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Parsing POMs
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed: <https://builds.apache.org/hudson/job/sling-trunk-1.5/ws/trunk> at hudson.remoting.Channel@3a7c7017:ubuntu1
	at hudson.FilePath.act(FilePath.java:753)
	at hudson.FilePath.act(FilePath.java:739)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423)
	at hudson.model.Run.run(Run.java:1362)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:145)
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 <https://builds.apache.org/hudson/job/sling-trunk-1.5/ws/trunk/bundles/commons/scheduler/pom.xml>: TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG seen ...<version>2.2.1-SNAPSHOT/version>\n\n    <name>... @34:11)  @ line 34, column 11

	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1327)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1110)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1957)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)
Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-parseable POM <https://builds.apache.org/hudson/job/sling-trunk-1.5/ws/trunk/bundles/commons/scheduler/pom.xml>: TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG seen ...<version>2.2.1-SNAPSHOT/version>\n\n    <name>... @34:11)  @ line 34, column 11

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339)
	at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
	at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
	at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1381)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1288)
	... 11 more


Jenkins build is back to normal : sling-trunk-1.5 #1191

Posted by Apache Jenkins Server <hu...@hudson.apache.org>.
See <https://builds.apache.org/hudson/job/sling-trunk-1.5/1191/changes>