Bug 450825

Summary:	"Java Build Path"-Page not reevaluated on ResourceFilter change
Product:	[Eclipse Project] JDT	Reporter:	Peter <p.rader>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	noopur_gupta
Version:	4.4.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Peter

2014-11-10 07:14:01 EST

I noticed i can not have a Folder as a Source Folder in the Build Path 
if the Folder is Filtered. If i remove the filter, the Java-Build-Path-Page still contains the old error-message.

Steps to reproduce:

1. Create a simple Java-Project.
2. Open Project Properties
3. Open the "Resource"-node.
4. Click on "Resource Filters"-node.
5. Add a Filter for the folder "src".
6. Press OK.
7. Clean/build project (a error occoure like: src not exists)
8. Open Project Properties.
9. Click on "Java Build Path" (the /src marked as missing)
10. Open the "Resource"-Node.
11. Click on "Resource Filters"
12. Remove the src-filter.
13. Press "Apply"
14. Click on "Java Build Path"-node.
Problem: Unfortunatelly the src-missing message still occoure.

Comment 1 Noopur Gupta

2014-11-14 01:29:35 EST

Reproducible with Eclipse 4.5 M3.
The Java Build Path page is not updated on Resource Filters change.
If you close and re-open the Properties page, it contains the updated state.

Comment 2 Eclipse Genie

2020-08-25 07:04:33 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.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2022-10-29 06:31:23 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.

--
The automated Eclipse Genie.