When using antcall a couple of suggestions: 1. if your build script is large, place your generalized targets in their own build file and use Ant instead.
2. always set inheritalAll to false as it appears not to work as stated in the docs (see my previous message on the subject). John-Mason Shackelford Software Developer NCS Pearson - Measurement Services 2510 North Dodge St. Iowa City, IA 52245 319-354-9200x6214 [EMAIL PROTECTED] > -----Original Message----- > From: Dave Draper [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 31, 2002 4:01 PM > To: 'Ant Users List' > Subject: RE: Parametrizing an ant task > > > You might also consider using <antcall> > > <antcall target="target name"> > <param name="param name" value="value"> > </antcall> > > - DD > > -----Original Message----- > From: Milind Nirgun [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 31, 2002 16:51 > To: Ant Users List > Subject: RE: Parametrizing an ant task > > > You can use the -D<property>=<value> option while running > ant. I am not sure > if thats what you wanted. > > -Milind > > > -----Original Message----- > > From: Saripalli, Raju [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, July 31, 2002 1:33 PM > > To: Ant-User (E-mail) > > Subject: Parametrizing an ant task > > > > > > > > Is it possible to parametrize an ant task ? > > > > For example (a very simple one) ... lets say I wanted to > > have a task that compiled all the classes in a specific package > > that could be specified as a run-time parameter > > > > How can this be done ? > > > > Thanks > > > > Raju > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
