Bug 299000 - Ant Builder Doesn't Appropriately Fail for Bad String Substitution
Summary: Ant Builder Doesn't Appropriately Fail for Bad String Substitution
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-06 17:59 EST by Sandeep Tamhankar CLA
Modified: 2019-09-06 15:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sandeep Tamhankar CLA 2010-01-06 17:59:42 EST
Build Identifier: 20090920-1017

Steps to reproduce:
* Edit global Ant properties to have a property "noexist" with value "${NOEXIST}" and property "exist" with value "${EXIST}"
* Add Eclipse String Substitution variable EXIST with value "i_exist"
* Create a build.xml file that echos the "exist" ant property to stdout.
* Create an Ant builder that runs build.xml with no extra args.  It should get the noexist and exist Ant property definitions from the global Ant settings.
* Run the builder.

Expected Result:
* The builder should complain that NOEXIST doesn't exist, or the NOEXIST string substitution should collapse to empty string.
* ${EXIST} should be substituted with "i_exist" on the way into Ant, and the console should show that in the echo output.

Actual Result:
* ${EXIST} doesn't get substituted; literally ${EXIST} is passed into Ant.

Reproducible: Always

Steps to Reproduce:
See above.
Comment 1 Olivier Thomann CLA 2010-01-06 22:57:24 EST
Move to Platform/Ant
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:32:15 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.