[imps] local install on Centos 6, BUILD SUCCESSFUL, but not quite ...
rancid.iodine at gmail.com
Wed Jan 18 04:11:32 PST 2012
Thank you both Martin and Thomas for your feedback. I think the
quickest way around this is
to get our network people to arrange for the firewall exception. I've
looked into it from the
java perspective, there's too much trial and error / research involved
and there are time
BTW doing a export _JAVA_OPTS='-Dhttp.proxyPort=myproxy.co.uk
to running the build.py doesn't seem to help either.
So with these firewall exceptions (for outgoing connections on ports
80 and 443) in mind, my question
is now this: to WHICH target hosts on the internet shall we authorise
the exceptions? The
network security people need to know, because naturally (as is their
nature :) they refuse
to set up an exception to "just anywhere".
Thomas you mentioned various dependencies are needed from
... and I could do
a big rgrep and some sedding for http://* in checker/ to see about
anything else, but there seems
to be so much that I'm not entirely sure where else is relevant in the
massive directory tree under
checker/. I can also see more items being needed (possibly) from
http://www.w3.org, and http://xml.org,
mentions of http://www.apps.ietf.org/, http://www.junit.org, and
possibly other places from other
directories outside checker/dependencies. Are the problem downloads
solely from .java modules? I would
assume so from what you're saying, but maybe not.
Does anyone have an idea of the exact list of targets, or how to
narrow these down, or shall I just
throw in anything I can find using rgrep/sed? I simply want to avoid
doing a to and fro with our
network people, and make build/py work the first time.
On Tue, Dec 13, 2011 at 1:40 PM, Martin Sharratt
<Martin.Sharratt at uwe.ac.uk
>* Are you behind a firewall, and do you need to set a proxy to get to the*>* Web? My server is and I had to create a firewall exception for the server*>* outbound on TCP ports 80 and 443. Re-running the build.py script then*>* completed successfully and I got a working validator.*>**>**>**>* Ideally java should honour any system proxy settings but it doesn’t seem*>* to. I’ve done the usual cursory research and have not really found any*>* simple way of setting a proxy for java – apparently it’s most often done*>* within the code. As usual this was a rush job so I’ve not had time to*>* research more thoroughly once I got a working system.*
I too believe this is a network issue
where the connection is made
tohttp://www.iana.org/assignments/character-sets, and note that you
make a local copy and override the URL by setting the
-Dorg.whattf.datatype.charset-registry system property; I don't know
how to set it through build.py though, as I never used it)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Implementors