As far as I undestand: yes.
Only the properties you give inside the task are given to ant or antcall.
The other properties are unset for the called target.
--
Jürgen Knuplesch
Geschäftsführer: Uwe Seltmann
HRB Stuttgart 17655
USt-IdNr.: DE 811944121
-Ursprüngliche Nachricht-
Von: C
But if you use or it is like you would start ANT a second
time. Therfore the properties
are set in the target or script that you call. The old values are lost if you
use the attribute
Inheritall=false
And using inside sets some properties to a value you define.
--
Jürgen Knuplesch
But in your original post you have specified the component in your batch file.
> > > > Batch file contents are :-
> > > >
> > > > set component=common
> > > > ant -f %build.dir%/component.xml
Where is the difference?
If you use Task or you can run the target with different
content of a property.
E.g.
I even use this in loops made with antcontrb.
--
Jürgen Knupleschwww.icongmbh.de
icon Systemhaus GmbH
with nested ?
Or use of s?
Jan
The reason I'm not using ant is that :-
1. My main build.xml script calls the component.xml script
numerous times.
2. Each time the component.xml script is called, the variable
'component' needs
> I am calling a dos batch file from an Ant script using the
> following code :-
>
>
>
>
>
>
>
>
> On the assumption that I get the Microsoft Windows Copyright
> info appear, I
> assume the above commands are running ok. The only trouble
> is, the contents
> / commands in the b
