Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Tue, 25 Sep 2012 11:44:07 +1100 (NCT)
From: "Stephen Kestle (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <1708630998.119772.1348533847625.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (IVY-1377) Resolution fails with zero-length file
 content
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Stephen Kestle created IVY-1377:
-----------------------------------

             Summary: Resolution fails with zero-length file content
                 Key: IVY-1377
                 URL: https://issues.apache.org/jira/browse/IVY-1377
             Project: Ivy
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0, 2.3.0
            Reporter: Stephen Kestle


[BasicURLHandler|https://svn.apache.org/repos/asf/ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/BasicURLHandler.java] decides that a zero length file is "UNAVAILABLE", presumably to force a resolution against a canonical http ivy repository.

(This behaviour is inherited from jayasoft).

There is no comment or test surrounding this decision, but it makes it difficult when there is a valid zero-length artifact and no network connection to an http ivy server.

My particular scenario is slightly more involved: I am ensuring that a local installed repository is complete and I achieve this by resolving {{http}} urls to the local file system. So my {{url.getProtocol()}} is "http", but my connection ends up as {{FileURLConnection}}.

I'd love the code to check the protocol as well (if it's trying to decide if the url is "canonical"), but at the least, can it be commented as to what it's trying to achieve by this behaviour?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira