[ https://jira.jboss.org/browse/JBBUILD-665?page=com.atlassian.jira.plugin.... ] Paul Gier updated JBBUILD-665: ------------------------------ Assignee: Paul Gier Fix Version/s: Repository Support 2010 I haven't seen this issue before. So you can see the POM in the directory listing, but you are not able to download it? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBBUILD-665?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBBUILD-665: ------------------------------------------- Funny enough, it seems that right now I can access https://repository.jboss.org/nexus/content/repositories/public/org/hibern.... At least through the browser. Using an empty directory for my local repo I still keep getting: mvn clean install -s ~/.m2/settings-tmp-repo.xml [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Hibernate Validator Aggregator [INFO] Hibernate Validator [INFO] Hibernate Validator Quickstart [INFO] Hibernate Validator Legacy [INFO] Hibernate Validator TCK Runner [INFO] Hibernate Validator Annotation Processor [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Hibernate Validator Aggregator 4.2.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ hibernate-validator-parent --- [INFO] [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java) @ hibernate-validator-parent --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ hibernate-validator-parent --- [INFO] Installing /Users/hardy/work/hibernate/git/validator/pom.xml to /Users/hardy/tmp/m2-clean/org/hibernate/hibernate-validator-parent/4.2.0-SNAPSHOT/hibernate-validator-parent-4.2.0-SNAPSHOT.pom [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Hibernate Validator 4.2.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ Downloading: http://repository.jboss.com/maven2/org/hibernate/hibernate-entitymanager/... Downloading: http://snapshots.jboss.org/maven2/org/hibernate/hibernate-entitymanager/3... Downloading: http://repo1.maven.org/maven2/org/hibernate/hibernate-entitymanager/3.6.0... [WARNING] The POM for org.hibernate:hibernate-entitymanager:jar:3.6.0.Final is missing, no dependency information available Downloading: http://repository.jboss.com/maven2/org/hibernate/hibernate-entitymanager/... Downloading: http://snapshots.jboss.org/maven2/org/hibernate/hibernate-entitymanager/3... Downloading: http://repo1.maven.org/maven2/org/hibernate/hibernate-entitymanager/3.6.0... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Hibernate Validator Aggregator .................... SUCCESS [0.333s] [INFO] Hibernate Validator ............................... FAILURE [7.797s] [INFO] Hibernate Validator Quickstart .................... SKIPPED [INFO] Hibernate Validator Legacy ........................ SKIPPED [INFO] Hibernate Validator TCK Runner .................... SKIPPED [INFO] Hibernate Validator Annotation Processor .......... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.698s [INFO] Finished at: Tue Dec 07 16:19:09 CET 2010 [INFO] Final Memory: 8M/81M [INFO] ------------------------------------------------------------------------ [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] [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/DependencyResolutionExce... [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :hibernate-validator -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBBUILD-665?page=com.atlassian.jira.plugin.... ] 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=ja... 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. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-665?page=com.atlassian.jira.plugi... ] Edward Ost commented on JBBUILD-665: ------------------------------------ I am having a very similar problem. I cannot resolve hibernate-validator 4.1 jar. I get the following error message during a maven build. Failure to find org.hibernate:hibernate-validator:jar:4.1.0.Final in http://nexus:8081/nexus/content/groups/production [my local nexus server] I am using my own local Nexus repository. When I browse my local Nexus index, I can find other hibernate validator 4.1 artifacts - except the actual jar artifact. When I browse manually online via a browser I can find the jar artifact. I am proxying https://repository.jboss.org/nexus/content/repositories/releases/ . I have tried with the public repository as well with the same result, https://repository.jboss.org/nexus/content/groups/public-jboss/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBBUILD-665?page=com.atlassian.jira.plugi... ] Paul Gier closed JBBUILD-665. ----------------------------- Resolution: Out of Date Closing this issue since the Nexus indexes are working correctly now. If the 404 errors happen again, please open a new issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira