Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 73219 invoked by uid 500); 22 Jan 2002 14:41:24 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 73208 invoked from network); 22 Jan 2002 14:41:23 -0000 From: "Carsten Ziegeler" To: Subject: RE: [PATCH] new build targets Date: Tue, 22 Jan 2002 15:43:09 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <003d01c1a352$5ce2ae90$90a4558b@vgritsenkopc> Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 22.01.2002 15:41:23, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 22.01.2002 15:41:24, Serialize complete at 22.01.2002 15:41:24 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Vadim Gritsenko wrote: > > > From: Nicola Ken Barozzi [mailto:barozzi@nicolaken.com] > > > > ----- Original Message ----- > > From: "Nicola Ken Barozzi" > > To: > > Sent: Tuesday, January 22, 2002 2:01 PM > > Subject: Re: [PATCH] new build targets > > > > > > > From: "Carsten Ziegeler" > > > > > > > David Crossley wrote: > > > > > ... > > > > > > > > > > Carsten, with the imminent release of 2.0.1 we do not want > > > > > to go messing around with the main build.xml file. Is it > possible > > > > > to set up a build.xml in the scratchpad to try these ideas? > > > > > Also, where should Ken's new class tools/src/UserInput.java > > > > > I do not see a matching place in scratchpad. Will i just make > > > > > the new directories? > > > > > > > > > ... So my suggestion is to put a small build > > > > files with Ken's target and UserInput class into our system and > this > > > > build file will then call the main build file. So we don't need to > > > > keep both build files in sync. > > > > > > Nice, I'll re-submit the patch with this layout. > > > > > > > Have a problem here. > > The interactive target calls other targets, but build targets in > "child" xml > > cannot call the parent targets, although they do inherit properties. > > Therefore I'm keeping it in build.xml unless someone has a better way. > :-/ > > How about reversing this: have your interactive.xml be "parent", and > original build.xml - "child", and from parent build, call child's > targets. > That was exactly the way I meant it. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org