Return-Path: Delivered-To: apmail-excalibur-dev-archive@www.apache.org Received: (qmail 59438 invoked from network); 2 Jul 2004 01:25:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Jul 2004 01:25:27 -0000 Received: (qmail 35051 invoked by uid 500); 2 Jul 2004 01:25:49 -0000 Delivered-To: apmail-excalibur-dev-archive@excalibur.apache.org Received: (qmail 34927 invoked by uid 500); 2 Jul 2004 01:25:46 -0000 Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Excalibur Developers List" Reply-To: "Excalibur Developers List" Delivered-To: mailing list dev@excalibur.apache.org Received: (qmail 34842 invoked by uid 99); 2 Jul 2004 01:25:43 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [131.172.42.21] (HELO latcs1.cs.latrobe.edu.au) (131.172.42.21) by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 01 Jul 2004 18:25:37 -0700 Received: from [192.168.0.240] (matchbox01.cs.latrobe.EDU.AU [131.172.41.101]) by latcs1.cs.latrobe.edu.au (8.12.11/8.12.10) with ESMTP id i621NVnU025220 for ; Fri, 2 Jul 2004 11:23:36 +1000 Message-ID: <40E4B928.6080604@realityforge.org> Date: Fri, 02 Jul 2004 11:23:52 +1000 From: Peter Donald User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Excalibur Developers List Subject: Re: questions: release management scripts References: <40E2D01A.3060103@jicarilla.org> <40E33D26.3090000@realityforge.org> <40E3954F.10100@jicarilla.org> <40E397C4.9010001@realityforge.org> <40E39CFB.40102@jicarilla.org> In-Reply-To: <40E39CFB.40102@jicarilla.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Leo Simons wrote: > it just grows out of control...where's my > > * prerequisite check > * argument validation > * error recovery > * sensible defaults > > should I write all that in xml? Should you write it at all? > the commands are right here: > > http://wiki.apache.org/excalibur/ReleaseManagement > http://wiki.apache.org/avalon/AvalonReleaseManagerHowto Egads. Some of this is not good. You can not reproduce a build from a tag which kinda defeats the purpose of a tag IMHO. Each separate component is not independent as they reference things outside their build hierarchy (even if it is just the parent project file). My suggestions is when you tag that you copy the entire trunk into tags directory. Something like svn copy \ https://svn.apache.org/repos/asf/excalibur/trunk https://svn.apache.org/repos/asf/excalibur/tags/MyComponent-Version-Release > question: if its so easy, why can't I find any examples of projects like > ours which have all this already done? Do you have any? I have several and I know of others but few are as anal and bogged down in politics as the Avalon process so most use slight modifications of the dist/release plugin. Mauro has worked a bit on the release plugin so maybe able to shed a bit of a better udnerstanding on it? Anyhow I will check in a basic maven.xml to perform basics of release process. I will skip generating mails and mailing them out as I think that is something a user should do. -- Cheers, Peter Donald "The only way to get rid of a temptation is to yield to it." - Oscar Wilde (1854-1900) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org For additional commands, e-mail: dev-help@excalibur.apache.org Apache Excalibur Project -- URL: http://excalibur.apache.org/