yes, the properties are being set as in a typical java.util.Properties file. some.property.key=some.value i have tested this file from my own properties reader within my codebase so i know it is OK as far as format goes. -----Original Message----- From: Anuj Agrawal To: ant-user@jakarta.apache.org Sent: 5/1/2001 6:23 PM Subject: Re: v1.3 -- problems retrieving properties from how are you setting the properties? assuming they are being set in the local.properties file, they should appear as: # e.g. weblogic.install.home=c:/whatever/the/path/is Anuj. "Webb, James" wrote: > Are there any known issues in 1.3 or config tricks for > retrieving properties from a properties file? > I have not seen any bugreports or patches for this kind > of issue. > > I am trying to set up a properties file containing > local configuration such as paths,etc. for each developer's > specific environment. > > /bldenv > ./build.xml --> main buildfile common to all developers > ./local.properties --> specific for each developer env > > > Things I have tried in my build.xml > > 1. using... > > > results in... > while in verbose mode when i echo any property > contained within the file it says... > > "Property ${weblogic.install.home} has not been set" > > I have also tested the property value with > the task and the task so I am > certain my problem is in the task > and not in . > > 2. using... > > > and placing the file in my CLASSPATH > > results... > I get the same result as before. > > 3. I have tried three different properties files > to make certain it was not an encoding issue. > This did not solve my problem. > > 4. My only workaround is to set these properties as > environment variables and grab them via > > I can get this to work but it is not as clean. > > Ant Version: 1.3 > OS: Windows 2000 > JDK: Sun 1.3.0_02