org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not transfer artifact <name-stuffs-removed>-pom:pom:1.0-SNAPSHOT from/to server.company.com (https://server.company.com/snapshot/): Not authorized. and 'parent.relativePath' points at wrong local POM @ line 3, column 10

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • We have Artifactory behind apache httpd (that requires authentication). When I try to build a maven project against an empty local repository, I get the stack trace that will be below. This happens both with maven2 and maven3. Also on a different maven project, that depends on a release version parent, this also happens. On the web-server log I can that Jenkins contacts the server, gets 401 -Authorization Required and does not even try to authorize. The maven project builds successfully in shell. Also if I build it in shell, and then delete everything but the parent pom(s), then the job in Jenkins builds fine downloading the required artifacts. So the problem seems to only affect downloadin the parent -artifacts. Parsing POMs Failed to transfer Could not transfer metadata <name-stuffs removed>:pom:1.0-SNAPSHOT/maven-metadata.xml from/to server.company.com (https://server.company.com/snapshot/): Not authorized. Failed to transfer Could not transfer artifact <name-stuffs-removed>-pom:pom:1.0-SNAPSHOT from/to server.company.com (https://server.company.com/snapshot/): Not authorized. 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 <name-stuffs-removed>-pom:pom:1.0-SNAPSHOT from/to server.company.com (https://server.company.com/snapshot/): Not authorized. and 'parent.relativePath' points at wrong local POM @ line 3, column 10 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:322) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1244) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1065) at hudson.FilePath.act(FilePath.java:783) at hudson.FilePath.act(FilePath.java:765) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:930) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:658) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462) at hudson.model.Run.run(Run.java:1404) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Description set: Finished: FAILURE
    via by Petteri Kauko,
  • We have Artifactory behind apache httpd (that requires authentication). When I try to build a maven project against an empty local repository, I get the stack trace that will be below. This happens both with maven2 and maven3. Also on a different maven project, that depends on a release version parent, this also happens. On the web-server log I can that Jenkins contacts the server, gets 401 -Authorization Required and does not even try to authorize. The maven project builds successfully in shell. Also if I build it in shell, and then delete everything but the parent pom(s), then the job in Jenkins builds fine downloading the required artifacts. So the problem seems to only affect downloadin the parent -artifacts. Parsing POMs Failed to transfer Could not transfer metadata <name-stuffs removed>:pom:1.0-SNAPSHOT/maven-metadata.xml from/to server.company.com (https://server.company.com/snapshot/): Not authorized. Failed to transfer Could not transfer artifact <name-stuffs-removed>-pom:pom:1.0-SNAPSHOT from/to server.company.com (https://server.company.com/snapshot/): Not authorized. 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 <name-stuffs-removed>-pom:pom:1.0-SNAPSHOT from/to server.company.com (https://server.company.com/snapshot/): Not authorized. and 'parent.relativePath' points at wrong local POM @ line 3, column 10 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:322) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1244) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1065) at hudson.FilePath.act(FilePath.java:783) at hudson.FilePath.act(FilePath.java:765) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:930) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:658) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462) at hudson.model.Run.run(Run.java:1404) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Description set: Finished: FAILURE
    via by Petteri Kauko,
  • Hudson build fail: Non-resolvable parent POM
    via Stack Overflow by Nicolas
    ,
  • Problems in setting up local Hudson CI for HBase
    via by Ramkrishna S Vasudevan,
  • Build failed in Jenkins: Thermostat #329
    via by Unknown author,
  • Since the upgrade to Jenkins-1.424.3, we are unable to build a native maven build on maven2 projects. Seems like it's trying to parse the project's pom, and it won't succeed. Might be related to the bigger strictness of M3, but from a m2 project point of view, it's a regression :-/. {quote} {noformat} L'ééchéance d'une alarme périodique a provoqué le lancement de ce job ln -s 2012-03-02_07-28-27 /ic/.jenkins/jobs/someproject-10.0/builds/517 failed: -1 Building on master Updating svn://somesvn/someproject-parent At revision 69492 no change for svn://somesvn/someproject-parent since the previous build No emails were triggered. Parsing POMs Failed to transfer Not authorized, ReasonPhrase:Unauthorized. ERROR: Echec à la lecture des POMs org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not transfer artifact fr.gid:someartefact:pom:11.5.0 from/to devRepo (http://repository.corp.net:8081/nexus/content/groups/public/): Not authorized, ReasonPhrase:Unauthorized. and 'parent.relativePath' points at wrong local POM @ line 5, column 10 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.invoke(MavenModuleSetBuild.java:1355) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1182) at hudson.FilePath.act(FilePath.java:758) at hudson.FilePath.act(FilePath.java:740) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:869) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:634) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:458) at hudson.model.Run.run(Run.java:1376) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:487) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:175) [WARNINGS] Skipping publisher since build result is FAILURE Saut de l&#39analyse sonar suite à un mauvais status de construction FAILURE Email was triggered for: Failure Sending email for trigger: Failure Sending email to: team@corp.fr Notifying upstream projects of job completion Finished: FAILURE {noformat} {quote} I didn't put that issue as BLOCKER since the solution is to recreate the job as freestyle one. But it's an awkward solution. PS : yes, I know the feature is still said to be beta. Cheers
    via by Baptiste Mathus,
    • org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not transfer artifact <name-stuffs-removed>-pom:pom:1.0-SNAPSHOT from/to server.company.com (https://server.company.com/snapshot/): Not authorized. and 'parent.relativePath' points at wrong local POM @ line 3, column 10 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:322) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1244) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1065) at hudson.FilePath.act(FilePath.java:783) at hudson.FilePath.act(FilePath.java:765) at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:930) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:658) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462) at hudson.model.Run.run(Run.java:1404) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238)

    Users with the same issue

    davidvanlaatum
    davidvanlaatum5 times, last one,
    Adarro
    Adarro1 times, last one,
    Unknown visitor1 times, last one,