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

Bug 398484

Summary:	Buildpath exclusion patterns not working on Mac OS X
Product:	[Eclipse Project] JDT	Reporter:	Marc <m.schipperheyn>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	stefan.fleiter
Version:	4.3
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:	stalebug

Description Marc

2013-01-18 07:29:30 EST

I recently switched to Mac OS and it seems that exclusion patterns are not working on Eclipse Juno.

On the build path I have a source folder entry for
src/main/resources

output folder: (Default output folder)
Included: (All)
Excluded: **/msa.properties;**jdbc.properties
Native library location: none
Ignore optional compile problems: no

However, whenever the project gets refreshed msa.properties and jdbc.properties are overwritten in the classes folder.

I also tried manually selecting the files as exclusion but this should work.

Perhaps there is some kind of weird permission thing going on but in any case, it seems like a bug.

Comment 1 Marc

2013-01-18 07:32:11 EST

the **jdbc.properties should be **/jdbc.properties.
I tried all sorts of combinations
*/msa.properties
**msa.properties
msa.properties

Comment 2 Stefan Fleiter

2013-07-25 08:23:16 EDT

Same here on Linux with Eclipse Kepler.

The m2e FAQ entry at least helped me to find the source of the problem and this bug:
http://wiki.eclipse.org/M2E_FAQ#Why_resource_folders_in_Java_project_have_excluded.3D.22.2A.22

So Eclipse breaks simple filtering of resources with maven like described here:
https://maven.apache.org/plugins/maven-resources-plugin/usage.html
Every refresh of the workspace overwrites the generated properties file.

Is there any known workaround in besides using the copy-resources goal:
https://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html
?

Comment 3 Eclipse Genie

2019-01-13 08:37:06 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.

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.