[Red5devs] Hudson builds are now marked unstable when javac or javadoc generates warnings
daccattato at gmail.com
Tue Jun 23 19:24:53 PDT 2009
I'm all for leaving them on. Is there a place that shows what produces a
CTO & Senior Engineer
On Tue, Jun 23, 2009 at 6:52 PM, Art Clarke <aclarke at xuggle.com> wrote:
> Recently I changed our Red5 build server to mark builds as unstable if they
> generate any javac or javadoc errors. You can see an example of the report
> I had already done a lot of work to make Red5 be 100% warning free under
> Java 1.5 and 1.6. A few check-ins ago the build became unstable because of
> some javadoc warnings in recent check-ins.
> Why javadoc warnings; because our users actually use the Javadoc (even if
> we don't). Now the current warnings for javadoc only show up if you
> explicitly add some javadoc and screw it up -- we don't give warnings if you
> don't add Javadoc.
> I've gone ahead and fixed the minor javadoc issues in tip of tree, but
> thought I'd let people know. If you'd rather not have builds be marked
> unstable because of warnings, I'm happy to turn it off (but my vote is to
> keep it on, as my experience has been the diligence results in higher
> quality code).
> If you want to ensure that your checkin isn't going to mark the build
> unstable, enable javadoc warnings in eclipse, and at least do this before
> every checkin:
> ant run-tests doc
> And if you want to be a really good citizen, run a system test (which I'd
> show you how to do if the Wiki was back up).
> - Art
> (p.s. I don't know why Hudson e-mail isn't working right now, but I'll try
> to fix it).
> xu‧ggle (zŭ' gl) v. To freely encode, decode, and experience audio and
> Use Xuggle to get the power of FFMPEG in Java.
> Red5devs mailing list
> Red5devs at osflash.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Red5devs