Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 64775 invoked from network); 22 Nov 2004 04:56:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Nov 2004 04:56:12 -0000 Received: (qmail 76128 invoked by uid 500); 22 Nov 2004 04:55:58 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 75746 invoked by uid 500); 22 Nov 2004 04:55:56 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 75701 invoked by uid 99); 22 Nov 2004 04:55:56 -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 [203.59.3.54] (HELO mail.iinet.net.au) (203.59.3.54) by apache.org (qpsmtpd/0.28) with SMTP; Sun, 21 Nov 2004 20:55:54 -0800 Received: (qmail 19586 invoked by uid 33); 22 Nov 2004 04:55:46 -0000 Received: from proxy.fairfax.com.au (proxy.fairfax.com.au [203.26.177.2]) by mail.iinet.net.au (IMP) with HTTP for ; Mon, 22 Nov 2004 12:55:46 +0800 Message-ID: <1101099346.41a17152308bc@mail.iinet.net.au> Date: Mon, 22 Nov 2004 12:55:46 +0800 From: Brett Porter To: Jakarta Commons Developers List , Martin Cooper Cc: Jakarta Commons Developers List , Dion Gillard Subject: Re: [jelly] Building 1.0-RC1 References: <16d6c620041121195611f4775d@mail.gmail.com> In-Reply-To: <16d6c620041121195611f4775d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 203.26.177.2 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Jelly doesn't have an Ant build file AFAIK, which this documentation assumes. Reading through those documents, Maven's prepare/perform release cycle does every step except for PGP signing which I do manually for distribution releases but is a planned feature (and obviously the sanity checks that things ended up in a certain web server). Some newer stuff may not be setup for Jelly (like being able to use announcement:mail to mail the announcement if you are happy with what was in changes.xml). This document covers the process: http://maven.apache.org/reference/developers/releasing-plugins.html I am currently rewriting the Maven documentation and will make this a bit more general so it can be used for other Maven projects. Cheers, Brett Quoting Martin Cooper : > On Mon, 22 Nov 2004 14:42:53 +1100, Dion Gillard > wrote: > > I'm in the process of building 1.0-RC1. > > > > CVS has been tagged. > > > > We really should document this process at some point :-) > > Do you mean the general Commons component release process: > > http://jakarta.apache.org/commons/releases/index.html > > or something more specific to Jelly? > > -- > Martin Cooper > > > > -- > > http://www.multitask.com.au/people/dion/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org