ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morrison, John" <John.Morri...@uk.experian.com>
Subject RE: [DISC] the simple stuff
Date Mon, 02 Apr 2001 13:38:59 GMT
That would be most appreciated.  Will the thought be migrated to Ant2 if it
isn't implemented in 1.x?

> -----Original Message-----
> From: Conor MacNeill [mailto:conor@cortexebusiness.com.au]
> Sent: 02 April 2001 2:14 pm
> To: ant-dev@jakarta.apache.org
> Subject: Re: [DISC] the simple stuff
> 
> 
> John,
> 
> I was thinking, in Ant 1.x think, of adding an "explicit" attribute to
> <ant> which would only pass those properties which you 
> explicitly list. Its
> the mode I would like to use mostly anyway, but I wouldn't change the
> current behaviour now.
> 
> Conor
> 
> ----- Original Message -----
> From: "Morrison, John" <John.Morrison@uk.experian.com>
> To: <ant-dev@jakarta.apache.org>
> Sent: Monday, April 02, 2001 8:05 PM
> Subject: RE: [DISC] the simple stuff
> 
> 
> > Is it possible to _stop_ properties being passed to sub ant tasks?
> >
> > For example, if I've a property called prjname defined in 
> projectA.xml
> and a
> > property called prjname defined in projectB.xml then I do...
> >
> > # projectA.xml
> > <property name="prjname" value="project A"/>
> > <target...>
> >   <ant dir="projectB" target="deploy"/>
> > </target>
> >
> > # projectB.xml
> > <property name="prjname" value="project B"/>
> > <target name="deploy">
> >   <echo message="${prjname}"/>
> > </target>
> >
> > How can I make the echo say project B?
> > > -----Original Message-----
> > > From: Stefan Bodewig [mailto:bodewig@apache.org]
> > > Sent: 02 April 2001 10:50 am
> > > To: ant-dev@jakarta.apache.org
> > > Subject: Re: [DISC] the simple stuff
> > >
> > >
> > > Peter Donald <donaldp@apache.org> wrote:
> > >
> > > >>>> * make properties fully dynamic, i.e. allow their value to
be
> > > >>>> * reassigned
> > > >>
> > > >>Conor MacNeill wrote:
> > > >>
> > > >>> They already are - just not by <property>. I still 
> want command
> > > >>> line override so either need scoping or an overall 
> control system
> > > >>> such as build.sysclasspath or whatever that is called.
> > > >
> > > > I thought they were only fully dynamic on first pass of 
> a task - ie
> > > > on subsequent invocations of same task the properties 
> have already
> > > > been interpreted ???
> > >
> > > You are right Pete, I think Conor (and others including 
> myself) just
> > > read this point as "make properties mutable via <property>".
> > >
> > > Stefan
> > >
> >
> >
> > 
> ==============================================================
> =========
> > Information in this email and any attachments are 
> confidential, and may
> > not be copied or used by anyone other than the addressee, 
> nor disclosed
> > to any third party without our permission.  There is no intention to
> > create any legally binding contract or other commitment 
> through the use
> > of this email.
> >
> > Experian Limited (registration number 653331).
> > Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
> >
> 

Mime
View raw message