Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 22528 invoked from network); 21 Nov 2006 05:59:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Nov 2006 05:59:13 -0000 Received: (qmail 40328 invoked by uid 500); 21 Nov 2006 05:59:23 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 40248 invoked by uid 500); 21 Nov 2006 05:59:22 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 40237 invoked by uid 99); 21 Nov 2006 05:59:22 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Nov 2006 21:59:22 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [88.84.142.181] (HELO v30161.1blu.de) (88.84.142.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Nov 2006 21:59:10 -0800 Received: (qmail 5942 invoked by uid 2525); 21 Nov 2006 06:53:51 +0100 To: general@gump.apache.org Subject: Re: Guidance on the Pluto Portal Gump build X-Draft-From: ("nnfolder:mail.gump-general" 11186) References: <44F6DCB4.2040603@jhu.edu> <6092360.post@talk.nabble.com> <7447037.post@talk.nabble.com> From: Stefan Bodewig Date: Tue, 21 Nov 2006 06:53:50 +0100 In-Reply-To: <7447037.post@talk.nabble.com> (CDoremus@hannaford.com's message of "Mon, 20 Nov 2006 09:51:13 -0800 (PST)") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org On Mon, 20 Nov 2006, wrote: > As Elliot has said, these alerts are because we have an incompatible > version of castor that gump uses in a Pluto branch where we will not > be upgrading any dependancies. If there is no development on that branch anymore, then we might as well stop building it and install it as a binary package. I've disabled the nag mails as a first step. > Can you configure gump to only go against our trunk SVN repository? We could, but since Gump and Maven 2 don't support each other (yet), we couldn't do anything with it. This will have to wait until Maven 2 builds are possible in Gump. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org