[jboss-jira] [JBoss JIRA] Commented: (JBBUILD-665) The nexus repository sometimes starts serving 404s for existing poms

[Paul Gier (JIRA)]

    [ https://issues.jboss.org/browse/JBBUILD-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574152#comment-12574152 ] 

Paul Gier commented on JBBUILD-665:
-----------------------------------

Edward, you might be able to resolve the problem if you avoid downloading our index.  There is an option in Nexus proxy repos to set Download Remote Index to "False".  That way your Nexus won't rely on our index.  It's not an ideal solution, but it may provide a workaround.  You might want to try asking the Sonatype guys if there is a better solution.

> The nexus repository sometimes starts serving 404s for existing poms
> --------------------------------------------------------------------
>
>                 Key: JBBUILD-665
>                 URL: https://issues.jboss.org/browse/JBBUILD-665
>             Project: JBoss Build System
>          Issue Type: Bug
>          Components: Maven Builds
>         Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100)
> Java version: 1.6.0_22
>            Reporter: Hardy Ferentschik
>            Assignee: Paul Gier
>            Priority: Critical
>             Fix For: Build Support 2011
>
>
> It seems sometimes the nexus repository starts serving 404s for dependencies. today I tried to rebuild Hibernate Validator from scratch and I kept getting:
> {noformat}
> [ERROR] Failed to execute goal on project hibernate-validator: Could not resolve dependencies for project org.hibernate:hibernate-validator:jar:4.2.0-SNAPSHOT: Could not find artifact org.hibernate:hibernate-entitymanager:jar:3.6.0.Final in jboss (http://repository.jboss.com/maven2) -> [Help 1]
> {noformat}
> Turned out that trying to access the URL https://repository.jboss.org/nexus/content/repositories/public/org/hibernate/hibernate-entitymanager/3.6.0.Final/hibernate-entitymanager-3.6.0.Final.pom returns a 404 which explains at least why the build fails. 
> This is not the first time I see this problem. A little while ago I deployed a SNAPSHOT of org.hibernate:hibernate-jpamodelgen. Even though I could see the SNAPSHOT in the directory listing I was not able to use the SNAPSHOT, because trying to access the pom would again return 404s. In the case of jpamodelgen disappeared then a day later (not sure exactly when. I just remember trying again some time a day later and it worked) 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira