[jira] Updated: (MAVEN-558) Errors incorrectly reported when an artifact does not exist on a remote repo

[ji...@codehaus.org]

The following issue has been updated:

    Updater: David Zeleznik (mailto:dzeleznik@ilog.com)
       Date: Wed, 9 Jul 2003 9:29 PM
    Comment:
Corrected getFile to throw a FileNotFoundException if the remote URL does not exist. Previously, getFile threw a generic Exception for this case.

Refactored getFile() to call a new overloaded method that never ignores errors and always throws exceptions. This should make it easier to maintain and verify that all of the exceptional cases are handled properly.

Changed method throws clauses to be more specific than just generic Exceptions.

Some small javadoc corrections.
    Changes:
             Attachment changed to HttpUtils.diff
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-558&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-558


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-558
    Summary: Errors incorrectly reported when an artifact does not exist on a remote repo
       Type: Bug

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             core
   Versions:
             1.0-beta-9

   Assignee: 
   Reporter: David Zeleznik

    Created: Wed, 9 Jul 2003 9:25 PM
    Updated: Wed, 9 Jul 2003 9:29 PM

Description:
The expected behavior of the DependencyVerifier is to check all remote repos for an artifact. If the artifact is successfully downloaded from at least one remote repo, the fact that the artifact may not exist on other remote repos is supposed to be ignored. Instead, the error is reported to the console "Error retrieving artifact from ...".

The logic in DependencyVerifier is actually correct. The problem is in r1.26 of HttpUtils.getFile() which incorrectly throws a generic Exception when a file is not found at a remote URL. Instead, HttpUtils should throw a FileNotFound exception for this case, which will then be caught and handled properly by DependencyVerifier.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org