Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 46005 invoked from network); 19 Jun 2009 08:05:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Jun 2009 08:05:55 -0000 Received: (qmail 53683 invoked by uid 500); 19 Jun 2009 08:06:06 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 53631 invoked by uid 500); 19 Jun 2009 08:06:06 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 53614 invoked by uid 99); 19 Jun 2009 08:06:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 08:06:05 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.24] (HELO gmp-eb-inf-2.sun.com) (192.18.6.24) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2009 08:05:54 +0000 Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n5J85KL7020831 for ; Fri, 19 Jun 2009 08:05:33 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KLH002006BWKJ00@fe-emea-10.sun.com> for derby-dev@db.apache.org; Fri, 19 Jun 2009 09:05:20 +0100 (BST) Received: from localhost (c596E47C1.dhcp.bluecom.no [193.71.110.89]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KLH00BMP7ST6K50@fe-emea-10.sun.com> for derby-dev@db.apache.org; Fri, 19 Jun 2009 09:05:18 +0100 (BST) Date: Fri, 19 Jun 2009 10:05:16 +0200 From: Knut Anders Hatlen Subject: Re: Hudson continuous build for Derby trunk In-reply-to: <4A3A5CBA.8050708@Sun.COM> Sender: Knut.Hatlen@Sun.COM To: derby-dev@db.apache.org Message-id: References: <4A2CDD6F.60804@Sun.COM> <4A2D177E.9040903@sun.com> <4A2D343E.5030506@Sun.COM> <54ac72d70906081714n31653aa8mde95fa4c80f64e01@mail.gmail.com> <4A2E794E.5070907@sun.com> <4A2FB07D.1000202@sun.com> <4A2FBA4D.70307@Sun.COM> <4A3A35C2.8090506@Sun.COM> <4A3A53BD.7070701@sun.com> <4A3A56B3.7000901@amberpoint.com> <4A3A5CBA.8050708@Sun.COM> User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.93 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Kristian Waagan writes: > Bryan Pendleton wrote: >> It seems like it would be useful for the Hudson build to build the docs, >> even if it doesn't publish them to the website, just to verify that they >> build successfully after each change. >> >> Similarly, if this isn't already occurring, it would be useful for the >> Hudson build to build Javadoc. I know that I often forget to verify the >> Javadoc build when checking a patch. > > Hi Bryan, > > That's a good idea, and I'll give it a try. > The only thing needed (I think) is that the ant script returns with an > error code when an error is found in the JavaDoc. Hopefully, that's > how it is already. I don't remember that we've had problems with javadoc errors. Are you talking about javadoc warnings (which we frequently introduce by accident)? If so, could the warnings plugin be used for this? http://wiki.hudson-ci.org/display/HUDSON/Warnings+Plugin > We have the choice of running this together with the build itself, or > as a separate job. > The downside by running it together with the build itself is that a > build error will hide the JavaDoc error. I think that's an acceptable trade-off. If the build is broken, I wouldn't care too much about javadoc problems until the build has been fixed. -- Knut Anders