-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
Platform: All, OS: All
Using Hudson 1.290 and the Checkstyle Plugin 2.6 with Sun JDK 1.6.0_12 on Linux
x86 I get the following error when building any kind of maven2 project (both
reactor and single module):
Module X: Parsing of file /opt/hudson/jobs/path/to/checkstyle-result.xml failed
due to an exception: org.xml.sax.SAXParseException: Content is not allowed in
prolog. at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1231)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.apache.commons.digester.Digester.parse(Digester.java:1685) at
hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:68) at
hudson.plugins.checkstyle.util.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:47)
at hudson.plugins.checkstyle.util.FilesParser.parseFile(FilesParser.java:146) at
hudson.plugins.checkstyle.util.FilesParser.parseFiles(FilesParser.java:125) at
hudson.plugins.checkstyle.util.FilesParser.invoke(FilesParser.java:81) at
hudson.plugins.checkstyle.util.FilesParser.invoke(FilesParser.java:22) at
hudson.FilePath.act(FilePath.java:434) at
hudson.plugins.checkstyle.CheckStyleReporter.perform(CheckStyleReporter.java:84)
at
hudson.plugins.checkstyle.util.HealthAwareMavenReporter.postExecute(HealthAwareMavenReporter.java:204)
at
hudson.maven.MavenModuleSetBuild$Builder.postExecute(MavenModuleSetBuild.java:640)
at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:290) at
hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170)
at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at
org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597) at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at
org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at
hudson.maven.agent.Main.launch(Main.java:158) at
hudson.maven.MavenBuilder.call(MavenBuilder.java:162) at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:579) at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:525) at
hudson.remoting.UserRequest.perform(UserRequest.java:92) at
hudson.remoting.UserRequest.perform(UserRequest.java:46) at
hudson.remoting.Request$2.run(Request.java:236) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at
java.util.concurrent.FutureTask.run(FutureTask.java:138) at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Is it possible that I have some misconfiguration or line endings mess up XML?
Thanks for helping,
Tamas