Regarding the docbook network connection exception:
On my notebook, I block unauthorized out-going connections, so I always get this error whenever running buildDocBook task.
I remember somebody said that checkstyle had the same problem, but it did not happen on my notebook.
I think I know the reason: in both case, there are configuration files (xml files) refering dtd or xsd schemas on the internet. If a validating parser is used internally, then the parser has to go online to retrieve the schema. The problem arises when network does not fail _completely_, the parse has to wait for a response until it times out.
It's pain. I always want to investigate whether it's possible to modify the tool somehow so that it won't go online to fetch the schema, but I am always short of time... and I end up only running buildDocBook on my workstation. Maybe we can log it as a trivial jira issue.
Cheers,
Cedric
Philip Johnson wrote:
Today's build failures have two causes:
(1) hackystat-ALL failed due to a compile error in hackyCourse (a JDom upgrade induced problem). That's totally my bad; I somehow spaced out hackyCourse when I went through all the modules.
I will check in the fixed version of hackyCourse later today and rebuild hackystat-ALL.
(2) Hackystat-UH failed due to:
Fatal Error! Failure reading file:///C:/CruiseControls/instance-UH/hacky/hackyBuild/build/docbook/tmp/in dex.docbook.xml Cause: java.net.ConnectException: Connection timed out: connect
This looks like it might be a transient network problem. To check, I am initiating a rebuild of Hackystat-UH right now. We'll see what happens in a half an hour.
Cheers, Philip
