Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 35319 invoked from network); 6 Apr 2004 21:46:22 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Apr 2004 21:46:22 -0000 Received: (qmail 16772 invoked by uid 500); 6 Apr 2004 21:46:05 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 16719 invoked by uid 500); 6 Apr 2004 21:46:05 -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 16684 invoked from network); 6 Apr 2004 21:46:05 -0000 Received: from unknown (HELO gadolinium.btinternet.com) (194.73.73.111) by daedalus.apache.org with SMTP; 6 Apr 2004 21:46:05 -0000 Received: from [81.128.112.140] (helo=oemcomputer) by gadolinium.btinternet.com with smtp (Exim 3.22 #25) id 1BAyOY-0004YK-00 for commons-dev@jakarta.apache.org; Tue, 06 Apr 2004 22:46:10 +0100 Message-ID: <008701c41c20$85075d00$8c708051@oemcomputer> From: "Stephen Colebourne" To: "Jakarta Commons Developers List" References: <20040406172448.51595.qmail@web60807.mail.yahoo.com> <1081273298.2846.50.camel@lorien.fas.harvard.edu> Subject: Re: [all] Shared build causes issues in releases Date: Tue, 6 Apr 2004 22:45:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thanks for sorting the problem with current builds. My point is more long term. I am proposing that a release of a single commons component should be complete (and tagged) internally, without reference to an external commons-build folder. To achieve this, a release must a) copy and rename commons-build/project.xml to project/project-common.xml b) edit project/project.xml to change the reference from the central source to the local one ATM release managers will have to remember to do this manually. (BTW, I needed the maven to work not to create a jar, but to fetch the dependencies of validator. Running 'maven clean' seemed like the quickest solution.) Stephen From: "Mark R. Diggory" > I've now added build and report sections that were missing to the > subproject project.xml files, please verify they contain what you want > for your project and adjust them to your liking if they do not. > > Maybe someone can review and do the same for the sandbox? > > On Tue, 2004-04-06 at 13:24, David Graham wrote: > > Well both the old and new versions cause problems for some set of projects > > so going back isn't really going to help. The common project.xml should > > not define a section because each component is different. For > > example, Validator has src/share instead of src/java. It should be up to > > each project to define how they build and what reports they want > > generated. > > > > Note that the sandbox-build's project.xml suffers from the same definition > > as commons-build used to and also needs to be changed. > > > > David > > > > --- Gary Gregory wrote: > > > Why can't we go /back/ to the version of commons-build that did not blow > > > up and /discuss/ it from there. Then we can change all projects in step. > > > > > > ? > > > > > > Thank you, > > > Gary > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Small Business $15K Web Design Giveaway > > http://promotions.yahoo.com/design_giveaway/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > -- > Mark R. Diggory > Software Developer - VDC Project > Harvard MIT Data Center > http://www.hmdc.harvard.edu > > > --------------------------------------------------------------------- > 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