Central isn't checked if pluginRepo specified in pom isn't reachable --------------------------------------------------------------------
Key: MNG-2516 URL: http://jira.codehaus.org/browse/MNG-2516 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: Brian Fox Attachments: pom.xml, settings.xml I ran into a case where we have a repo defined in our pom. In some installations, this repo isn't reachable. To work around this, we synched our repo locally and setup file based remote repos and pluginrepos. However when checking for plugins, central wasn't being checked because it was stopping at the repo it couldn't reach. I was able to replicate this with a simple pom and settings.xml that are attached. Put them in a folder and run mvn -s ./settings.xml install. It seems like failures accessing one repo will cause the whole build to fail. Shouldn't it at least check other repos like central before giving up completely? -- 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