infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15815) Maven build can't find SNAPSHOT parent pom on repository.apache.org
Date Sun, 21 Jan 2018 01:22:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333364#comment-16333364
] 

Chris Lambertus commented on INFRA-15815:
-----------------------------------------

You tell me .. I have no idea how Maven manages dependencies. I'm really only concerned with
the "could not find artifact" error. Perhaps the underlying issue here is not with Nexus,
but with the way your build manages dependencies?


> Maven build can't find SNAPSHOT parent pom on repository.apache.org
> -------------------------------------------------------------------
>
>                 Key: INFRA-15815
>                 URL: https://issues.apache.org/jira/browse/INFRA-15815
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Jenkins
>            Reporter: Robert Munteanu
>            Assignee: Chris Lambertus
>            Priority: Major
>
> For several Jenkins jobs we have a problem where a parent pom deployed on repository.apache.org
is not found. For instance, on https://builds.apache.org/job/sling-org-apache-sling-testing-paxexam-1.8/21/console:
> java.io.IOException: remote file operation failed: /home/jenkins/jenkins-slave/workspace/sling-org-apache-sling-testing-paxexam-1.8
at hudson.remoting.Channel@4ed6a58:H35: 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 find artifact org.apache.sling:sling:pom:33-SNAPSHOT
and 'parent.relativePath' points at no local POM @ line 24, column 11
> Building the project locally works as expected:
> Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/sling/sling/33-SNAPSHOT/maven-metadata.xml
> Downloaded from apache.snapshots: https://repository.apache.org/snapshots/org/apache/sling/sling/33-SNAPSHOT/maven-metadata.xml
(594 B at 554 B/s)
> Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/sling/sling/33-SNAPSHOT/sling-33-20180109.083736-32.pom
> Downloaded from apache.snapshots: https://repository.apache.org/snapshots/org/apache/sling/sling/33-SNAPSHOT/sling-33-20180109.083736-32.pom
(58 kB at 58 kB/s)
> Since the snapshots repository definition is part of the ASF parent pom, there is nothing
for us to adjust.
> Failures were seen on H35, H32, H26 and ubuntu-2, so this does not look like a slave-specific
issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message