Pinar,
The real question is: Are the properties set by the time they're being
referenced in your build? Properties that chain off of other properties
the way yours do can end up with the "... not set" being printed out
during a -verbose run even though the values do are set once everything is
parsed (there was a change put through awhile back that affected this, but
I don't remember now in which file). In other words, as long as they're
set once you need them to be, you can ignore that message.
Diane
--- Pinar Bicioglu <[EMAIL PROTECTED]> wrote:
>
>
> -----Original Message-----
> From: Nico Seessle [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 18, 2001 3:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: -verbose option
>
>
> ----- Original Message -----
> From: "Pinar Bicioglu" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, April 18, 2001 9:11 PM
> Subject: RE: -verbose option
>
>
> > yes, there is. It's as the following:
> >
> > <property file="build.properties" />
> >
>
> Ok, and the file containing the properties you wish to set is named
> "build.properties"?
>
> That's right!
>
> And located in the current working directory from which you are
> executing
> Ant?
>
> So it is in the same directory with build.xml file.
>
> And the line is in a location in your build.xml you are sure that is
> executed?
>
> yes I am sure about that because first it says;
>
> [property] Loading D:\sandbox\Engineering\dev\java\build.properties
> Property ${jdk122root} has not been set
> Property ${jdk118root} has not been set
>
> Thanks!
>
=====
([EMAIL PROTECTED])
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
