Bug 3458

Summary:	Resource folders containing source (1G4CKG9)
Product:	[Eclipse Project] JDT	Reporter:	Andre Weinand <andre_weinand>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	2.0
Target Milestone:	2.1 M1
Hardware:	All
OS:	Windows NT
Whiteboard:

Description Andre Weinand

2001-10-10 22:55:29 EDT

AW (13.11.00 11:26:36)
	In a sample application I'm using hierarchical resource folders 
containing files of various types as my testinput.

	In LeapFrog these files are kept separate from the package hierarchy and
	are not compiled even if they bear the file extension ".java".

	This is no longer supported in Eclipse. If I import a hierarchal 
resource folder I end up having a flat list of new packages for all leaf 
folders, some
	empty and some containing *.java files.
	

CM (3/21/01 11:35:08 AM)
	It is important to get the resource story correct early.
	Because resource support in VAJ was not designed in at the beginning,
	it is probably not possible to ever have resources as first-class 
citizens.
	In LeapFrog, resources and resource folders are a natural part of the 
UI.
	Please make the Eclipse Java IDE similar to LeapFrog in this respect.

Comment 1 Martin Aeschlimann

2001-10-15 06:25:28 EDT

moved to active

Comment 2 DJ Houghton

2001-10-24 07:09:32 EDT

PRODUCT VERSION:
	JDT Mini Test Pass Nov 15, Eclipse 011, IBM JDK 1.2.2

Comment 3 Dirk Baeumer

2002-07-25 06:28:42 EDT

There in nothing we can do, since the Java Model treats very child below a 
package fragment root as a package. So we can distinguish them

The only way to work around this is to use source folders and "normal folders'.

Moving to JDT Core. Please close if you are not going to change this.

Comment 4 Philipe Mulet

2002-07-30 07:12:15 EDT

No action planned on this front. Indeed, if these resources are not to be 
compiled, they should not be placed in a source folder.

Comment 5 Philipe Mulet

2002-07-30 07:13:47 EDT

Closing