[ http://jira.codehaus.org/browse/MNG-2049?page=comments#action_65383 ]
Christoffer Hammarström commented on MNG-2049: ---------------------------------------------- I can verify this. Right now repo1.maven.org is down for some reason, and does not answer any requests. Maven goes looking for every missing pom there, and fails the build when repo1.maven.org does not answer. The output is: Downloading: http://repo.imcode.com/maven2/com/imcode/imcms/imcms/3.1.2/imcms-3.1.2.pom [WARNING] Unable to get resource from repository imcode (http://repo.imcode.com/maven2) Downloading: http://repo1.maven.org/maven2/com/imcode/imcms/imcms/3.1.2/imcms-3.1.2.pom [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: com.imcode.imcms:imcms Reason: Error getting POM for 'com.imcode.imcms:imcms' from the repository: Error transferring file com.imcode.imcms:imcms:pom:3.1.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), imcode (http://repo.imcode.com/maven2) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5 seconds [INFO] Finished at: Mon May 15 16:10:25 CEST 2006 [INFO] Final Memory: 4M/7M [INFO] ------------------- > Timeouts in POM downloads cause the build to fail > ------------------------------------------------- > > Key: MNG-2049 > URL: http://jira.codehaus.org/browse/MNG-2049 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.2 > Reporter: Matthew Beermann > > > We have a number of jars in our repository that don't have POMs, e.g. > third-party libraries, etc. Maven happily downloads the jar anyway, and > issues a warning that there's no POM - except, sometimes, it just fails > instead. See the build log below. If I were to rerun Maven again, it might > fail on a different jar, or it might succeed. I can't seem to find any rhyme > or reason to it... > I agree that a missing POM merits a warning, but if the jar is there, it > shouldn't be failing the build! > Downloading: http://prdwebdev11/repository/j2ee/j2ee/1.3.1/j2ee-1.3.1.pom > [WARNING] Unable to get resource from repository prdwebdev11 > (http://prdwebdev11/repository) > Downloading: http://repo1.maven.org/maven2/j2ee/j2ee/1.3.1/j2ee-1.3.1.pom > [INFO] > ---------------------------------------------------------------------------- > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] Error building POM (may not be this project's POM). > Project ID: j2ee:j2ee > Reason: Error getting POM for 'j2ee:j2ee' from the repository: Error > transferring file > j2ee:j2ee:pom:1.3.1 > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > prdwebdev11 (http://prdwebdev11/repository) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
