Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 11099 invoked from network); 10 Dec 2004 11:19:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Dec 2004 11:19:55 -0000 Received: (qmail 80898 invoked by uid 500); 10 Dec 2004 11:19:54 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 80837 invoked by uid 500); 10 Dec 2004 11:19:53 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: 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 80824 invoked by uid 99); 10 Dec 2004 11:19:53 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from bodewig.bost.de (HELO bodewig.bost.de) (62.96.16.111) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 10 Dec 2004 03:19:52 -0800 Received: (from bodewig@localhost) by bodewig.bost.de (8.11.6/8.11.6) id iBABJnS06919; Fri, 10 Dec 2004 12:19:49 +0100 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: general@gump.apache.org Subject: Re: [RT] Gump 3.0 X-Draft-From: ("nnfolder:mail.gump-general" 5802) References: <41B4E798.8030709@apache.org> From: Stefan Bodewig Date: Fri, 10 Dec 2004 12:19:49 +0100 In-Reply-To: (Stefan Bodewig's message of "Wed, 08 Dec 2004 16:09:20 +0100") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wed, 08 Dec 2004, Stefan Bodewig wrote: > On Mon, 06 Dec 2004, Stefano Mazzocchi wrote: > >> So, here is my first suggestion: split gump in three stages. >> >> 1) metadata aggregation >> 2) build >> 3) build data use > > Sounds good. One additional thing. I'd love to have part 2 separated into at least three steps that can get invoked indiviually: 2a) SCM update 2b) syncing updated working copy with workspace 2c) building With "traditional Gump" it has been possible to modify classes in the workspace and rebuild using Gump. This has been very useful in resolving Gump problems in the past. Right now I don't see an easy way to do this. For example, I "fixed" the commons-jelly-tags-ant build by patching the jelly-util taglib. I verified it would fix the Gump build by applying my patch locally and only building commons-jelly-tags-util and after that commons-jelly-tags-ant. Using current Gump my local patch would have been blown away by CVS updates or syncs - unless I applied it in what is supposed to be a clean checkout and disconnected from the network. Also, just building commons-jelly-tags-util and commons-jelly-tags-ant without rebuilding Ant and all that seems to be impossible right now (I may be wrong, though). Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org