Bug 23470 - Configure Ant does not handle errors very well
Summary: Configure Ant does not handle errors very well
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M4   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: core, ui
Depends on:
Blocks:
 
Reported: 2002-09-12 09:21 EDT by Markus Kohler CLA
Modified: 2002-12-10 17:35 EST (History)
0 users

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 Markus Kohler CLA 2002-09-12 09:21:11 EDT 
I upgraded from 2.0 to 2.0.1 and after that I had a problem with one of my build
files (My problem might have nothing to do with the update, I don't know). I got
always a message "ant runner internal error". Unfortunately there was no message
available, neither in the console log nor in the eclipse .metadata/.log file. 

As it turned out I had specified ${workspace_loc:SgCommon} instead of 
${workspace_loc:/SgCommon}
Comment 1 Darin Swanson CLA 2002-09-30 15:49:18 EDT 
Markus, I can't reproduce your problem on 2.0.1 or otherwise.  Can you attach a 
build file that exhibits the problem and the exact steps to reproduce the 
problem?
Comment 2 Markus Kohler CLA 2002-10-02 03:05:21 EDT 
I already switched to build M1 and it seems to work there. 

I think it didn't depend on the build file itself.

In M1 I can specify ${workspace_loc:SgCommon} or 
${workspace_loc:/SgCommon} as the working dir and it seems to work. 

You should probably check if it is intended that ${workspace_loc:SgCommon} works
too.
Comment 3 Darin Swanson CLA 2002-11-12 21:59:37 EST 
Moving to M4
Comment 4 Darin Swanson CLA 2002-12-10 17:35:27 EST 
The resource expander is able to handle both cases.