Bug 270517 - ant.executor.class property cannot be used to set the executor from within eclipse
Summary: ant.executor.class property cannot be used to set the executor from within ec...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-30 16:23 EDT by Patrick Hart CLA
Modified: 2019-09-06 15:30 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Hart CLA 2009-03-30 16:23:27 EDT
The ant.executor.class property is ignored because eclipse explicitly sets the ant executor in InternalAntRunner.run(List) with new ExecutorSettor().setExecutor(getCurrentProject());  I would like to be able to set a custom executor.

It appears as if the only thing the EclipseDefaultExecutor does that the DefaultExecutor does not is project.addReferance("eclipse.ant.targetVector",v);
If this is necessary, it would be possible for ExecutorSettor to wrap an instance of the executor given as ant.executor.class to set that reference appropriately.

Alternatively ExecutorSetter could wrap the instance returned by Project.getExecutor(), but if ExecutorSetter gets called multiple times it would then keep wrapping the wrapped tasks.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:30:10 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.