Bug 21478 - Insufficient Ant activation error reporting
Summary: Insufficient Ant activation error reporting
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.1 M2   Edit
Assignee: Jared Burns CLA
QA Contact:
URL:
Whiteboard:
Keywords: core
Depends on:
Blocks:
 
Reported: 2002-07-11 06:43 EDT by Philipe Mulet CLA
Modified: 2002-10-04 12:00 EDT (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 Philipe Mulet CLA 2002-07-11 06:43:09 EDT 
Build R2.0

In an Eclipse R1.0 workspace, running under Eclipse R2.0, I tried to launch an 
Ant script, and got an error during execution saying:

===================
Problem Running External Tool

 - External tool failed to run
 - Reason:
     Could not find one or more classes. Please check the Ant classpath
===================

Now, what am I supposed to do in order to fix this ? I can check the Ant 
classpath, but how can I figure what is missing exactly ?
Comment 1 Philipe Mulet CLA 2002-07-17 05:12:37 EDT 
The R1.0 workspace was technically a 2.0 level workspace with Eclipse 1.0 dev 
contents. However, since last time I had opened it, the Ant classpath 
configuration had changed, and wasn't correct any longer.

The problem is that the error message doesn't tell you anything about what it 
needs, furthermore, given Ant is provided with Eclipse, some auto-detect 
feature would be much appreciated to initialize this setting (in case the 
custom one isn't right).
Comment 2 Darin Swanson CLA 2002-09-25 14:29:31 EDT 
Autodetection of the default ant classpath has been fixed.
Basically if the user has not set a custom classpath, the ant classpath is kept 
up to date.
See bug 19899.

Definately still a problem for reporting what is missing.
Comment 3 Darin Swanson CLA 2002-09-30 10:42:39 EDT 
The error messages include the name of the class that could not be found or no 
class def could be found for.
The error message is also logged to plugin log.
Comment 4 Darin Swanson CLA 2002-09-30 10:43:36 EDT 
Changes to AntRunner#run(IProgressMonitor)

Please verify (Jared)
Comment 5 Jared Burns CLA 2002-10-04 12:00:19 EDT 
Verified.