Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 318161

Summary:	"Filtered resources" field doesn't 'remember' its settings
Product:	[Eclipse Project] JDT	Reporter:	Leonardo <leonardompm>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	amj87.iitr, daniel_megert, jarthana, srikanth_sankaran
Version:	3.4
Target Milestone:	4.3 M7
Hardware:	All
OS:	All
Whiteboard:

Description Leonardo

2010-06-28 06:55:12 EDT

Build Identifier: I20080617-2000

Our team has been dealing with this issue for quite some time now. It all started when we noticed that, from time to time, the XML files required by our projects were not being 'compiled'. Later we found out this filter, "Filtered resources" at Java/Compiler preferences. It was enough to empty this field and it all started working again, but it still happened from time to time. Not until recently, I've noticed that whenever I reopened my workspace the "Filtered resources" field was there all filled up again. I trully believe the field should 'remember' that it has been emptied and not assume this is some mistake and repopulate itself all alone. (Setting priority to normal because it's too annoying to fix this every single day).

Reproducible: Always

Steps to Reproduce:
1. Open Window > Preferences > Java > Compiler
2. Clean the field "Filtered resources" and let the rebuild happen
3. Close the Eclipse platform and then reopen it
4. Open Window > Preferences > Java > Compiler again
5. The field should be all filled up again

Comment 1 Ayushman Jain

2010-06-28 07:57:30 EDT

Leonardo, I couldnt reproduce this on 3.6. Your'e using a fairly old build and in all probability, the problem seems to have got fixed now.

Can you use a newer build and check? Thanks!

Comment 2 Ayushman Jain

2010-07-05 07:48:26 EDT

I intend to close this as WORKSFORME. Leonardo, did you get a chance to try a newer build?

Comment 3 Leonardo

2010-07-05 08:29:39 EDT

Reverted the version of the component to 3.4 since the problem happens there.

I'm affraid for me it's not a simple matter of upgrading to the newest version, since the tools are designated for my team to work with. I haven't tried but even if it works, my team won't be able to use it until another team "authorizes" the upgrade.

Comment 4 Dani Megert

2013-04-08 10:40:12 EDT

Works for me using R4.2.2. Maybe you ran into bug 230050 back then.