Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328160 - Eclipse.refreshLocal does not cause run configurations to be updated
Summary: Eclipse.refreshLocal does not cause run configurations to be updated
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-19 12:58 EDT by chris CLA
Modified: 2021-11-08 13:40 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description chris CLA 2010-10-19 12:58:37 EDT
Build Identifier: 20100218-1602

I have an ant task that creates a new .launch file.
If the same task executes an Eclipse.refreshLocal on the directory containing the new .launch file (depth zero, one, or infinite) the run menu does not contain the new run configuration.  

If i manually refresh the directory the new launcher becomes available.

Reproducible: Always

Steps to Reproduce:
1.Place a new .launch file in some directory
2.Execute an an ant task that performs an Eclipse.refreshLocal on that directory
3.The new launcher should appear in the Run As drop down (run button)
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:13:31 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.
Comment 2 Eclipse Genie CLA 2021-11-08 13:40:02 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.