Bug 18682 - [ExternalTools] "tool's file does not exist"/"could not find one or more classes"
Summary: [ExternalTools] "tool's file does not exist"/"could not find one or more clas...
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 major (vote)
Target Milestone: 2.0 F3   Edit
Assignee: Ryan Cooper CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-06-03 06:47 EDT by Ilja Preuss CLA
Modified: 2002-09-18 13:58 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilja Preuss CLA 2002-06-03 06:47:40 EDT
For some of my ant scripts I get the error message "tool's file does not exist 
for the external tool named /project/build.xml" after hitting the run button of 
the ant wizard.

The scripts are working fine from the command line.
Comment 1 Rodrigo Peretti CLA 2002-06-03 09:05:12 EDT
Moving to Platform UI for comments.
Comment 2 Nick Edgar CLA 2002-06-03 09:39:28 EDT
Please indicate build number.
Are you using the Run Ant... action or a configured external tool?
Does it always give this behaviour for the same script, or is it intermittent?
Comment 3 Ilja Preuss CLA 2002-06-04 06:46:27 EDT
Mhh, strangely enough I am no longer able to reproduce the problem. Now I am 
getting an "Ant runner internal error" without any output in the Log Console 
for every script (by both using "Run Ant..." and "Run|External Tools..."). I am 
using build F2.
Comment 4 Ilja Preuss CLA 2002-06-04 06:50:40 EDT
In the "Edit External Tool" Dialog, I see a warning "Tool working directory 
does not exist or is invalid". The working directory field has the 
content "${container_loc}".
Comment 5 Ilja Preuss CLA 2002-06-04 06:55:55 EDT
Sorry, obviously I am getting confused... %-(

With "${workspace_loc}" as working directory, the warning disappears, but the 
error remains. The error is always reading "*External tool* runner internal 
error", though...
Comment 6 Nick Edgar CLA 2002-06-04 10:59:02 EDT
Please attach your .log file.
Comment 7 Ilja Preuss CLA 2002-06-05 03:14:50 EDT
I don't get any log-entry by this bug.

To verify this, I deleted the .log file, restarted Eclipse and reproduced the 
error. I didn't get any .log file created.
Comment 8 Nick Edgar CLA 2002-06-05 23:34:42 EDT
Are you on the F2 build (20020602)?
Do you get a {workspace_loc} var in the file name field when you choose the 
build file in the workspace?
Comment 9 Ilja Preuss CLA 2002-06-06 02:19:25 EDT
I am using the F2 build and get an ${workspace_loc:<filepath>} entry for the 
build file.
Comment 10 Simon Arsenault CLA 2002-06-06 09:29:02 EDT
Can you include in this problem report the value of all the fields when you 
edit the tool configuration for /project/build.xml We can then create the same 
here and debug it. Also, could you include the build.xml file?
Comment 11 Ilja Preuss CLA 2002-06-06 09:56:28 EDT
Location: ${workspace_loc:/_Test/build.xml}
Arguments:  ${ant_target:all}
Directory: 

<project default="all">
	<target name="all"/>
</project>
Comment 12 Ryan Cooper CLA 2002-06-07 13:15:22 EDT
I have not been able to reproduce this with the given steps.
Comment 13 Nick Edgar CLA 2002-06-07 16:30:11 EDT
Ilja, could you please try to reproduce this using the latest build?

Tod, could you also please try to reproduce this?
Comment 14 Tod Creasey CLA 2002-06-10 08:12:20 EDT
I cannot reproduce either.
Comment 15 Ilja Preuss CLA 2002-06-10 08:33:23 EDT
I will try to reproduce it using the F3 build when it is available. 
Unfortunately I currently don't have the resources to try an integration build.
Comment 16 Ryan Cooper CLA 2002-06-10 14:40:22 EDT
Can not reproduce.

Please reopen if problem re-occurs.
Comment 17 Ilja Preuss CLA 2002-06-14 05:04:05 EDT
Now, in F3, the error message changed to "Could not find one or more classes. 
Please check the Ant classpath."

The ant classpath is containing ant.jar, jakarta-ant-1.4.1-optional.jar and 
xerces.jar
Comment 18 Simon Arsenault CLA 2002-06-14 08:53:29 EDT
Rodrigo, since this error comes from ant core, what needs to be done to fix it? 
Could the build.xml file using ant 1.5 instead of 1.4?
Comment 19 Rodrigo Peretti CLA 2002-06-14 09:01:27 EDT
If you mean the error "Could not find one or more classes. 
Please check the Ant classpath." it means that the JARs in the Ant preferences 
do not exist anymore. Could you verify that this is true? If the location of 
the ant.jar or xerces.jar does not exist on disk, try clicking "Restore 
defaults" in the Ant preferences. It should work.
Comment 20 Ilja Preuss CLA 2002-06-14 09:05:05 EDT
Rodrigo, that did the trick! I didn't notice that the folder names of the ant 
plugin were changed - Doh!

Thank you very much for your help!