ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51829] New: URLResource.connect() logs as error when URL.openConnection() fails
Date Thu, 15 Sep 2011 19:23:03 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51829

             Bug #: 51829
           Summary: URLResource.connect() logs as error when
                    URL.openConnection() fails
           Product: Ant
           Version: 1.8.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Core
        AssignedTo: notifications@ant.apache.org
        ReportedBy: rich@steelezone.net
    Classification: Unclassified


URLResource.connect() logs the IOException thrown by URL.openConnection() 
(line 376 in URLResource.java for Ant 1.8.2).  Normally, this would be
OK--exception I've wrapped the URL resource in a <restrict> with an <exists>
selector because in my case it can be OK if the URL isn't found.

The net result is we're getting errors logged even though the build doesn't
fail.

Is there really a reason to log this as an error?  Isn't the exception an
indication that something might have gone wrong, but we should let the caller
assume responsibility for determining if this is really an error?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message