I bet it's the external references of the xml schemas in the docbook xml
file. The docbook task needs to retrieve those schema files from
external sites, which can take a very long time if those sites do not
respond.
The resolver.jar is supposed to solve this problem. I am no expert on
this. But the basic idea is that if you have all the schemas locally,
then you can configure the resolver the use the local version.
On my computer, there was a time the docbook task always hanged in the
middle (looks like waiting for responses from the net). But recently,
everything's ok. I have no idea what I did, but it works fine now.
(Hopefully, you can find the answer).
Frankly, I hate those absolute external references in xml files.
Cheers,
Cedric
Hongbing Kou wrote:
Hi, Hackers,
Most of my recent work is on suspicion editing so I ran task
hackyCore_Build.buildDocBook a lot. The problem I have is that it takes
excessively long time to run this task on my laptop. The latest run took my
laptop 17 minutes 33 seconds, which is way too long. The strange thing is that
it takes only 2-3 minutes on my desktop. My suspicion is that my ANT has some
old jar files but a clean installaltion of ANT did not make it faster at all.
Upgrading from JDK 1.4.2 to JDK 5 did not help as well.
How long does it take on your computer to build Hackystat laptop? Did you ever
experience this problem? Mike pointed out that my desktop has dual CPUs, but
my laptop is not very inferior to it on many other tasks. I will be very
appreciated if you know what might go wrong.
Thanks,
Hongbing
