Noel J. Bergman ha scritto: > 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
What about a "| grep -v javadoc" while you write the mail body? I think it is useful anyway to keep them even if we are not able to fix email notifications. (e.g: I monitor the target folder once a day) The build is also useful for users experiencing some bug with 2.3.1 and wanting to help us testing trunk to tell us if it is reproducible with it. I would like to have nightly for everyone of our projects: some day ago I had to do a nightly build for jspf to let an user test a bugfix. Where do you run this nighly builds? ASF hardware or external resources? You just wrote on general@ that ASF is planning allowing other java based tools in the future: what about continuum? A continuum instance with all of our projects would be great. I'm not a member, but I could help configuring our instance if help is needed. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
