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

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik commented on JBBUILD-665:
-------------------------------------------

Bugger. Seems I dug my own grave by  using this custom settings file (~/.m2/settings-tmp-repo.xml ). I just did not want to overwrite my local repo and build a new local repo into a separate directory. Turns out the settings file had indeed the wrong JBoss repo configuration. Cut & Paste of the URLs does of course give you 404s. And in the cases were it worked I relied on the auto-completion of my browser bar :( At least this mystery is solved. 

A somehow related question - what could be the reason that a build (from the same directory) using different local repositories one time succeeds and one time fails? 
Using 'mvn clean install' (running against my existing repo compiling Validator) works fine. 'mvn clean install -s ~/.m2/settings-tmp-repo.xml ' (after fixing the repo configuration) gets the same error as seen on Hudson - http://hudson.qa.jboss.com/hudson/job/hibernate-validator-trunk/76/jdk=java16_default,label=RHEL5_any/consoleFull

There is of course http://jira.codehaus.org/browse/MNG-4900, but I thought it was fixed with Maven 3.0.1 and given that it worked against my local repository I thought all is fine again.

> The nexus repository sometimes starts serving 404s for existing poms
> --------------------------------------------------------------------
>
>                 Key: JBBUILD-665
>                 URL: https://jira.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: Repository Support 2010
>
>
> 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