Community
Participate
Working Groups
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.
moved to active
PRODUCT VERSION: JDT Mini Test Pass Nov 15, Eclipse 011, IBM JDK 1.2.2
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.
No action planned on this front. Indeed, if these resources are not to be compiled, they should not be placed in a source folder.
Closing