Description
When resolving dependencies (downloading pom.xml or jar files), the logging output does not offer any information as to WHY the respective file was not downloaded. Consider the following output (snipped from a standard "mvn install" run):
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
Downloading: http://download.java.net/maven/1//javax.xml.ws/jars/jaxws-api-2.1-1.jar
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
As you can see, a maven proxy is queried, and then re-checked, but no clear statement is made as to WHY this happens (could be connection problems, not found - 404, not authenticated - 401).
Attachments
Issue Links
- is depended upon by
-
MNG-4578 Missing local repository results in ResourceNotFoundException while resolving artifact(s), parent
-
- Closed
-
