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

Failed to parse POMs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • core
    • None
    • Jenkins ver. 2.60.3
      Windows server 2012
      maven 3.3.9
      JDK 8 IBM
      Maven Integration plugin 3.0
      Pipeline Maven Integration Plugin 3.0.1

      Hi,

      I'm facing a problem since two days and cannot find the solution.

      I have a maven project with the following structure (flat folders) :

      • proj-setup (parent)
      • proj-jar
      • proj-api
      • proj-web
      • proj-config

      When I use a maven job, I have the following error :

      {{ Parsing POMs}}
      {{ Failed to transfer Could not transfer artifact foo.foo-api-common:foo-api-pom-common:pom:0.0.1 from/to corporate (}}
      {{ http://mavenrepo/m2/corporate): }}
      {{ Failed to transfer Could not transfer artifact foo.foo-api-common:foo-api-pom-common:pom:0.0.1 from/to appsupp-team-delivery (http://mavenrepo/m2/appsupp-team-delivery): Host name may not contain blanks}}
      {{ Failed to transfer Could not transfer artifact foo.foo-api-common:foo-api-pom-common:pom:0.0.1 from/to centralMirror (http://mavenrepo/m2/central): Host name may not contain blanks}}
      {{ ERROR: Failed to parse POMs}}
      {{ org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:}}
      {{ [FATAL] Non-resolvable parent POM: Could not transfer artifact foo.foo-api-common:foo-api-pom-common:pom:0.0.1 from/to pclo (http://mavenrepo/m2/pclo): Host name may not contain blanks and 'parent.relativePath' points at wrong local POM @ line 6, column 10at 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)}}
      {{ at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1125)}}
      {{ at hudson.FilePath.act(FilePath.java:998)}}
      {{ at hudson.FilePath.act(FilePath.java:976)}}
      {{ 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:490)}}
      {{ at hudson.model.Run.execute(Run.java:1735)}}
      {{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)}}
      {{ at hudson.model.ResourceController.execute(ResourceController.java:97)0}}
      {{ at hudson.model.Executor.run(Executor.java:405)}}

      I thought there was a problem on the declaration of my parent pom in proj-setup :

      <parent>
      {{ <groupId>foo.foo-api-common</groupId>}}
      {{ <artifactId>foo-api-pom-common</artifactId>}}
      {{ <version>0.0.1</version>}}
      {{ </parent>}}

      So I removed it and then got a similar error on the first dependency

      ERROR: Failed to parse POMs
      {{ org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:}}
      {{ [ERROR] Non-resolvable import POM: Could not transfer artifact org.springframework.boot:spring-boot-dependencies:pom:1.4.2.RELEASE from/to pclo (}}
      {{ http://mavenrepo/m2/pclo}}
      {{ ): Host name may not contain blanks @ line 52, column 16}}

       

      The job is using a custom settings and global settings (retrieved from SCM with the project).

      I've also created a freestyle job (windows batch command) in order to do it differently and assert my settings are good :

       

      set JAVA_HOME=D:\tools\jdks\8.0\SR8_FP35\x86_64
      {{ set M3_HOME=D:\tools\apache-maven-3.3.9}}
      {{ set PATH=%JAVA_HOME%\bin;%M3_HOME%\bin;%PATH%}}
      {{ mvn clean install -f proj-setup/pom.xml -B -e -Dmaven.repo.local=D:\tools\jenkins_home\maven-repositories\0 --global-settings toolbox/ci-config/mvn_settings.xml --settings toolbox/ci-config/settings_global.xml --activate-profiles daily-integration}}

       

      This build runs just fine...

      I don't understand why jenkins is crying. Where can I find the mvn command it tries to execute ? In fact, I don't even think it executes maven, it is internal code :

      org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
      {{ at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)}}

      Please help ! I pull one's hair out...

            Unassigned Unassigned
            vdl Jerome Van Der Linden
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: