Bug 13878

Summary:	Request to support folders for resource copy filters
Product:	[Eclipse Project] JDT	Reporter:	Stef van Dijk <svandijk>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	philippe_mulet
Version:	2.0
Target Milestone:	2.0 M6
Hardware:	All
OS:	All
Whiteboard:

Description Stef van Dijk

2002-04-16 09:20:38 EDT

I would like to request the ability to specify an entire directory (folder) 
when defining the resources not to be copied to the output folder during a 
build.
Our plugin currently supports having a META-INF folder per source folder, so in 
order to avoid the "This resource is a duplicate and was not copied to the 
output folder" errors produced by the java builder, we would like to filter the 
entire directory from being copied over.
The syntax could be of the form "META-INF/*" and should support being relative 
as we won't know the name of the source folders in advance.

Comment 1 Kent Johnson

2002-05-03 15:42:52 EDT

How about a list of folder names to skip... no wildcards, just the relative 
subfolder names?

So if we're about to copy a resource file src1/p1/zzz/a/b/test.txt and the 
folder property included 'zzz', then we would skip it.

Ok? Any folder name matching a segment name in getProjectRelativePath() would 
stop the resource from being copied.

Comment 2 Philipe Mulet

2002-05-06 07:07:09 EDT

Then folders would be indicated using a trailing '/' (e.g. 'zzz/').

Comment 3 Stef van Dijk

2002-05-06 09:38:29 EDT

Works for me.

Comment 4 Kent Johnson

2002-05-07 12:50:18 EDT

Our other choice is to change the filter to pattern match against 
resource.getProjectRelativePath() instead of resource.getName()... then you 
could specify:

*.txt
*/META-INF/*
*-INF/*.txt

Comment 5 Kent Johnson

2002-05-20 14:14:36 EDT

Added support for "Meta-Inf/" to match a folder named Meta-Inf... no wildcards 
are supported.