Bug 206362 - property file property expansion does not work when importing files in the run as -> ant build... option
Summary: property file property expansion does not work when importing files in the ru...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-15 14:24 EDT by Kevin CLA
Modified: 2019-09-06 15:36 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin CLA 2007-10-15 14:24:19 EDT 
when adding an ant .properties file to an ant build run target within eclipse (via the configuration editor window) and running the ant target, the properties file doesnt expand properties correctly.  for example, if a property file has the following properties:

base.dir = C:\dev\project
my.project = ${base.dir}\my\project.txt

and that file is included in the manner described above, then the ant task will read the ${my.project} property as ${base.dir}\my\project.txt instead of C:\dev\project\my\project.txt as one should expect.
Comment 1 James Loghry CLA 2008-01-09 23:07:40 EST 
The only way to get around this in ANT at the moment is to use the <property /> task.  Unfortunately, changing the property task within the actual script is more time consuming and error prone than simply specifying the property file within the configuration editor window when right-clicking on the script and going to Running->Ant Build...
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:36:03 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.