Summary: | ANT_HOME not set on first run of Ant tool | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Ian Jefferies <eclipse_bugzilla> | ||||
Component: | Ant | Assignee: | Jared Burns <jared_burns> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | Keywords: | core, ui | ||||
Version: | 2.1 | ||||||
Target Milestone: | 2.1 M5 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Ian Jefferies
2002-12-22 17:33:56 EST
Created attachment 2867 [details]
Test case build file to demonstrate the bug
A few bugs here: not setting the system property early enough not clearing the system property if the user had unset ant_home launch specific settings were not honored. Fixed in AntCorePreferences and InternalAntRunner, AntRunner and AntUtil. Please verify (Jared). I was about to report some additional information to help in the bug hunt. I moved my external Ant installation to another dir, and found the old E:\ant appearing instead of the null-like value of ${ant.home}, suggesting a history problem. Sounds like you caught it, many thanks. Verified. |