Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 28800 invoked from network); 17 May 2005 17:37:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 May 2005 17:37:12 -0000 Received: (qmail 44178 invoked by uid 500); 17 May 2005 08:54:19 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 44100 invoked by uid 500); 17 May 2005 08:54:18 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 44059 invoked by uid 99); 17 May 2005 08:54:17 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from natsmtp00.rzone.de (HELO natsmtp00.rzone.de) (81.169.145.165) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 17 May 2005 01:54:16 -0700 Received: from 172.26.0.5 (242.Red-213-97-135.pooles.rima-tde.net [213.97.135.242]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j4H8rsGj024060 for ; Tue, 17 May 2005 10:53:55 +0200 (MEST) Subject: Re: [Plugins] cannot build whiteboard plugins. From: Thorsten Scherler To: dev@forrest.apache.org In-Reply-To: <428907CE.9070000@apache.org> References: <1116241540.7711.4.camel@localhost.localdomain> <1116249562.10601.4.camel@localhost.localdomain> <428907CE.9070000@apache.org> Content-Type: text/plain Date: Tue, 17 May 2005 10:53:55 +0200 Message-Id: <1116320035.5812.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Mon, 2005-05-16 at 21:51 +0100, Ross Gardler wrote: > Thorsten Scherler wrote: > > I found the revision. > > > > Doing "svn up r170336" will bring back the version that is working. > > > > @Ross did you tested the whiteboard plugins before you checked in the > > above revision? Any ideas how I can I fix it in "trunk"? > > > > Not directly no. The above revision simply replaces the whole buildfile > with an import of the one in the main plugins directory. Since I > published all the docs for the plugins in the main directory I kind of > figured it would work. > Yeah, I figured but I did not had time to dig in and find a fix. > Sorry, I *should* have tested. > No worries, mate. This things can happen. The spam attack (which killed my providers mail server) took me much more time then to find the revision number. ;-) > Something strange is happening here, because now the main plugin build > displays the same problem you describe and the target hasn't been > present since r164079. I'll work out what happened and correct it ASAP. > Hmm, the target "checkout-deployed-docs" does not exit (or better said cannot be found). > Ross BTW @Rick you have been running into the same problem only for the main plugins. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)