Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 2.1.0-M1
-
Fix Version/s: None
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Environment:Linux - Ubuntu 8.04 Server - JDK Sun 1.6.0_06 - Maven 2.0.9
-
Complexity:Intermediate
-
Number of attachments :
Description
When the local repository is not writable, the error messages when downloading an artifact does not allow to pin down the issue quickly.
Maven only reports that the artifact cannot be downloaded, and the root cause is displayed as :
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository
No message in the trace indicates a problem with the local repository.
The full trace with a clean local repository is attached.
Wagon is correctly throwing a TransferFailedException - in 2.1.0-M2-SNAPSHOT, you can use -X to reveal the error "Specified destination directory cannot be created". The problem is that Maven is tossing out the message from that exception in the resolution process.