It's a hog while running, but not during the build (and it's only a hog
because the cache is kept in the target dir and is wiped out during the
clean goal).
There's absolutely no reason it shouldn't build and install during
bootstrap.
I'm just going to sit in the corner and blame the leaky c
LinkCheck is a bit of a hog...
Peter Royal wrote:
On Sunday, June 1, 2003, at 08:23 PM, Mike Bowler wrote:
Ben Walding wrote:
This typically is not the fault of LinkCheck. You can remove the
LinkCheck dir and it will just fail on the next one.
That's the behaviour I was expecting but is not
On Sunday, June 1, 2003, at 08:23 PM, Mike Bowler wrote:
Ben Walding wrote:
This typically is not the fault of LinkCheck. You can remove the
LinkCheck dir and it will just fail on the next one.
That's the behaviour I was expecting but is not actually what happens.
I deleted the linkcheck directo
Ben Walding wrote:
This typically is not the fault of LinkCheck. You can remove the
LinkCheck dir and it will just fail on the next one.
That's the behaviour I was expecting but is not actually what happens.
I deleted the linkcheck directory and the bootstrap build completed
successfully. Unles
This typically is not the fault of LinkCheck. You can remove the
LinkCheck dir and it will just fail on the next one.
Typically it is caused by running out of memory (I couldn't bootstrap
until I added 1000M of VM to my box). Later builds increase the memory,
but if your OS doesn't have it ava
Trying to build the LinkCheck plugin (from cvs) on OS/X results in a
"Bus error" which terminates the build. As a result, I can't run the
bootstrap build at all.
I'm not entirely sure what a bus error is but some google searches would
indicate that it's usually a problem with the JVM itself.
