Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8430

Error parsing POM (Maven 2.2.1) after Update Hudson 1.392

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • maven-plugin
    • None
    • Maven 2.2.1, Hudson 1.392, SLES 11

      Just upgraded to hudson 1.392 and now fails, nothing changed on maven settings...
      Help appreciated

      [...]
      Started by user anonymous
      Building remotely on tclxs75
      [...]
      Found mavenVersion 2.2.1 from file jar:file:/var/hudson/tools/Maven_2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
      Parsing POMs
      failed to transfer Error transferring file: central
      ERROR: Failed to parse POMs
      hudson.util.IOException2: remote file operation failed: /var/hudson/workspace/SMART at hudson.remoting.Channel@ba63a2:tclxs75
      	at hudson.FilePath.act(FilePath.java:752)
      	at hudson.FilePath.act(FilePath.java:738)
      	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:690)
      	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:526)
      	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
      	at hudson.model.Run.run(Run.java:1362)
      	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:400)
      	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-resolvable parent POM: Could not transfer artifact org.eumetsat:eumetsat:pom:1 from/to central (http://central): Error transferring file: central and 'parent.relativePath' points at wrong local POM @ line 25, column 11
      
      	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1129)
      	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:983)
      	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1925)
      	at hudson.remoting.UserRequest.perform(UserRequest.java:114)
      	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-resolvable parent POM: Could not transfer artifact org.eumetsat:eumetsat:pom:1 from/to central (http://central): Error transferring file: central and 'parent.relativePath' points at wrong local POM @ line 25, column 11
      
      	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
      	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:382)
      	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1096)
      	... 11 more
      Finished: FAILURE
      
      [...]
      

          [JENKINS-8430] Error parsing POM (Maven 2.2.1) after Update Hudson 1.392

          stezis added a comment -

          <corrected text>

          stezis added a comment - <corrected text>

          stezis added a comment -

          Reverted to 1.391 and works again, so looks like a regression to me (introduced by making MVN3 work in 1.392?)
          As well, if I look at the console output, there seems to be "much" different stuff going on now.
          1.391:

          Started by user anonymous
          Building remotely on tclxs75
          [...]
          Parsing POMs
          [SMART_Reports] $ /var/hudson/tools/JDK_6.21/bin/java -cp /var/hudson/maven-agent.jar:/var/hudson/tools/Maven_2.2.1/boot/classworlds-1.1.jar hudson.maven.agent.Main /var/hudson/tools/Maven_2.2.1 /var/hudson/slave.jar /var/hudson/maven-interceptor.jar 45527 /var/hudson/maven2.1-interceptor.jar <===[HUDSON REMOTING CAPACITY]===>\ufffd\ufffd\ufffdchannel started
          Executing Maven: -B -f /var/hudson/workspace/SMART_Reports/pom.xml checkstyle:checkstyle pmd:pmd findbugs:findbugs 
          [...]
          


          Stephan

          stezis added a comment - Reverted to 1.391 and works again, so looks like a regression to me (introduced by making MVN3 work in 1.392?) As well, if I look at the console output, there seems to be "much" different stuff going on now. 1.391: Started by user anonymous Building remotely on tclxs75 [...] Parsing POMs [SMART_Reports] $ / var /hudson/tools/JDK_6.21/bin/java -cp / var /hudson/maven-agent.jar:/ var /hudson/tools/Maven_2.2.1/boot/classworlds-1.1.jar hudson.maven.agent.Main / var /hudson/tools/Maven_2.2.1 / var /hudson/slave.jar / var /hudson/maven-interceptor.jar 45527 / var /hudson/maven2.1-interceptor.jar <===[HUDSON REMOTING CAPACITY]===>\ufffd\ufffd\ufffdchannel started Executing Maven: -B -f / var /hudson/workspace/SMART_Reports/pom.xml checkstyle:checkstyle pmd:pmd findbugs:findbugs [...] – Stephan

          hagzag added a comment -

          +1 here.
          I noticed this happens when relative-path is used in the project.
          Projects with version based resolution do not have this issue.

          hagzag added a comment - +1 here. I noticed this happens when relative-path is used in the project. Projects with version based resolution do not have this issue.

          Olivier Lamy added a comment -

          Olivier Lamy added a comment - see JENKINS-8390

          stezis added a comment -

          works with the fix provided for JENKINS-8390

          stezis added a comment - works with the fix provided for JENKINS-8390

            olamy Olivier Lamy
            stezis stezis
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: