Summary: | Insufficient Ant activation error reporting | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Ant | Assignee: | Jared Burns <jared_burns> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | Keywords: | core |
Version: | 2.0 | ||
Target Milestone: | 2.1 M2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philipe Mulet
2002-07-11 06:43:09 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). 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. 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. Changes to AntRunner#run(IProgressMonitor) Please verify (Jared) Verified. |