cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: [PATCH] new build targets
Date Tue, 22 Jan 2002 14:37:48 GMT
> From: Nicola Ken Barozzi [mailto:barozzi@nicolaken.com]
> 
> ----- Original Message -----
> From: "Nicola Ken Barozzi" <barozzi@nicolaken.com>
> To: <cocoon-dev@xml.apache.org>
> Sent: Tuesday, January 22, 2002 2:01 PM
> Subject: Re: [PATCH] new build targets
> 
> 
> > From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
> >
> > > 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.

Can this work?

Vadim


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message