Community
Participate
Working Groups
Hi, I am having problem to get package explorer to show java source files which are located in the source folders. My Java build path setting is like this: Source folders on build path: myproject/java included: com/db/; com/beans/ excluded: com/db/sub1/; com/db/sub2/; com/db/sub3 In my package explorer, I can not see folders com/db or com/beans at all. Other folders under com package, however, did show up. So it seems to be doing the opposite of what I want. I looked into the filter and the settings were fine. I then changed the "included" to point to "com/", and the "db" and "beans" folders magically showed up in the package explorer. So my question is: why doesn't package explorer show the folders in the included path in the first instance? Can package exploer hide all those files in the excluded folders? Thanks, Wenqi Dwyer
Wenqi, can you please create a test project showing the problem, zip it and attach it to the bug report. This would be a help.
Created attachment 17371 [details] Test project files Please find attached the Test project files. There is a file named "eclipse-screenshot.doc" that has a screen shot of my eclipse setting. Any hint on how to solve the problem is greatly appreciated. Thanks.
Created attachment 17382 [details] Screen shot This works for me without a problem (see attached screen shot). Do you have any special filters set.
Setting to remind since this seems to be a setup/filter problem.
Created attachment 17389 [details] package explorer filter setting Please see attached my package explorer filter setting. I do not see anything particular that might have caused my package explorer not showing those "included" packages. Any suggestion?
OK, I think I have it figured out. I changed the package explorer layout from "Hierarchical" to "flat", and the package explorer did show the included folders correctly. If I change the layout back to "hierarchical", the included folders disappear from the package explorer. Please verify. I think it's a eclipse bug??
Wenqi, please see bug 65240 for the glorz details of this problem. We plan to fix this in the 3.1 release cycle.
*** This bug has been marked as a duplicate of 65240 ***