Bug 195696 - Ant editor should be able to flag tasks can't be resolved as warnings
Summary: Ant editor should be able to flag tasks can't be resolved as warnings
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-06 15:16 EDT by Mike Reid CLA
Modified: 2019-09-06 16:16 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 Mike Reid CLA 2007-07-06 15:16:38 EDT 
In the default ANT run settings, the JRE is launched separate from the workspace JRE. For a user who is writing an Ant script which makes use of the package Eclipse based tasks (projectImport, workspaceRefresh, etc.) this is counter-intuitive.

Any user who creates an Ant script which uses one of these tasks and then selects Run as > Ant Build will get an error. 

It would be nice if the tool would look at the classpath of the run config (using the default settings if one has not yet been created) and flag warnings for those tasks that would not be resolved if the build were run.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:16:12 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.