Hi Noel,
If you make a tail -20 of log (and full log... pkzip & attach as file?) :-)
Saludos,
Guillermo
----- Original Message -----
From: "Noel J. Bergman" <[EMAIL PROTECTED]>
To: "James Developers List" <server-dev@james.apache.org>
Sent: Sunday, August 19, 2007 12:00 AM
Subject: Nightly Build Reports Too Big (again)
Something has been changed in the past couple of weeks, and the nightly
build e-mails are broken again. Since the last one, containing 94K, was
sent on August 10th, we have not only gone over 100K of output, we're at
239K of output!
As a point of reference, back in December, the breakdown was:
Deprecation messages for main compile: ~20K
Deprecation messages for junit compile: ~12K
JUnit output: ~20K
xdocs output: ~ 6K
JavaDoc messages: ~30K
----
~88K
We then worked to eliminate all of the Deprecation messages, and had
plenty
of room for additional unit test output. Now we have:
[javadoc] Loading source file [...]: ~143K
[javadoc] Misc javadoc messages ~ 29K
[copy] Copying <n> files to <dir>: ~ 9K
[mkdir] Created dir: <dir>: ~ 9K
messages. Any idea how we can eliminate some of this extraneous garbage
so
that the build report can be posted? Or should I just shut down the
nightly
builds because no one cares anyway?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
