Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0.4
-
Fix Version/s: 2.0.5
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Complexity:Intermediate
-
Testcase included:yes
-
Number of attachments :
Description
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 seems to have been fixed back in 2.0.5 when the repository blacklisting was added. The attached pom builds fine.