[
https://issues.jenkins-ci.org/browse/JENKINS-8902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159585#comment-159585
]
evernat commented on JENKINS-8902:
----------------------------------
Bonjour Arnaud,
A year later, could you confirm that there is still an issue with this maven
error?
> Maven 3 : Unclear errors reporting in parse pom phase
> -----------------------------------------------------
>
> Key: JENKINS-8902
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8902
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Environment: Maven 3.0.2 + Hudson 3.998
> Reporter: Arnaud Héritier
>
> I can give you a testcase if required.
> You just need to have a project with a module and a wrong inheritance
> (non-standard inheritance which doesn't set relativePath).
> I think I provided one like that in another issue :-)
> With Maven 3 you have this error which is clear :
> {code}
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project
> org.exoplatform.cs:exo.cs.web.webservice:2.2.0-Beta2-SNAPSHOT
> (/Users/arnaud/Code/eXo/cs-trunk.svn/web/webservice/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact
> org.exoplatform.cs:cs:pom:2.2.0-Beta2-SNAPSHOT in exo-fr-mirror
> (http://repository.exoplatform.org/public) and 'parent.relativePath' points
> at wrong local POM @ line 4, column 11 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> In Jenkins in the parsing pom phase the error is reported like :
> {code}
> Found mavenVersion 3.0.2 from file
> jar:file:/home/swfhudson/data/tools/maven-3.0.x/lib/maven-core-3.0.2.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
> No emails were triggered.
> Parsing POMs
> failed to transfer Unable to locate resource in repository
> failed to transfer Unable to locate resource in repository
> failed to transfer Unable to locate resource in repository
> 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 find artifact
> org.exoplatform.cs:cs:pom:2.2.0-Beta2-SNAPSHOT in exo-central-server
> (http://repository.exoplatform.org/public/) and 'parent.relativePath' points
> at wrong local POM @ line 4, column 11
> [FATAL] Non-resolvable parent POM: Could not find artifact
> org.exoplatform.cs:cs:pom:2.2.0-Beta2-SNAPSHOT in exo-central-server
> (http://repository.exoplatform.org/public/) and 'parent.relativePath' points
> at wrong local POM @ line 4, column 11
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
> at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
> at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
> at
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1152)
> at
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:995)
> at hudson.FilePath.act(FilePath.java:756)
> at hudson.FilePath.act(FilePath.java:738)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:702)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:532)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420)
> at hudson.model.Run.run(Run.java:1362)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:406)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:145)
> {code}
> Less easier to understand :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira