harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Petrenko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-523) [classlib] [build] unable to download dependences if behind the firewall
Date Mon, 10 Jul 2006 12:44:30 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-523?page=comments#action_12420059 ] 

Alexey Petrenko commented on HARMONY-523:

Yep, these are misleading properties.

Another issue with these proprties that they are not documented. So I suggest to also add
few lines to the ant error message which suggests to run "ant fetch-depends".

BTW Known workaround for this issue is to set  "ANT_OPTS= -Dhttp.proxyHost=<host> -Dhttp.proxyPort=<port>
-Dftp.proxyHost=<host> -Dftp.proxyPort=<port>" environment variable.

> [classlib] [build] unable to download dependences if behind the firewall
> ------------------------------------------------------------------------
>          Key: HARMONY-523
>          URL: http://issues.apache.org/jira/browse/HARMONY-523
>      Project: Harmony
>         Type: Improvement

>   Components: Classlib
>  Environment: win32
>     Reporter: Alexei Zakharov
>     Priority: Trivial
>  Attachments: enable_proxy.patch
> Automatic downloading of dependent jars doesn't work if system is located behind the
> ant -f make/depends.xml download
> ends with:
> download:
>      [echo] Fetching depends/jars/xalan-j_2.6.0/xalan.jar
>       [get] Getting: http://www.ibiblio.org/maven/xalan/jars/xalan-2.6.0.jar
>       [get] Error getting http://www.ibiblio.org/maven/xalan/jars/xalan-2.6.0.jar to
> C:\Java\harmony\enhanced\classlib\trunk\make\depends.xml:70: The following error occurred
while executing this line:
> C:\Java\harmony\enhanced\classlib\trunk\make\depends.xml:117: java.net.ConnectException:
Connection timed out: connect
> As far as I understand make\depends.xml (revision 410065) does not utilize http.proxyHost
& http.proxyPort props defined in depends.properties . Attached patch corrects this situation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message