Community
Participate
Working Groups
Build ID: M20080911-1700 Steps To Reproduce: Build ID: M20080911-1700 -- pulled from eclipse download site on 9/26. Steps To Reproduce: 1. Create a Dynamic Web priject 2. Right click project - Web Tools - Add Javascript Support 3. Add new file test.js under WebContent 4. Add WebContent directory to the javascript library 5. Switch to javascript perspective - will see webcontent with "js" icon BUT no contents. Can't see the test.js Sometimes if you add the folder and refresh then remove it and add it back again to the library then the file appears - but not always. Will not see the test2.JS is the /JS folder. File is on the filesystem and can be viewed from the java perspective. More information: I have lots of files in existing projects that are all uppercase. Major effort to change all the names since our webcontainer is case sensitive. More information:
Disregard the test2.JS comments they are for a different bug report -- they were in the buffer and I accidentally pasted them in...
I saw some additional problems... 1. Create a web project. 2. Remove WebContent as a source folder and add it back as a Library folder (via project properties.) In the JavaScript perspective the WebContent folder shows up only under the JavaScript Resources node. It shows up as a normal folder and files which is wrong. It also lets you add files and folders. In the Project Explorer it also shows up under the JavaScript Resources node. It also displays another node called Referenced Libraries.
I suspect we're not rescanning library folders routinely, or responding to resource change notifications in them since they're not supposed to change that often.
Categorizing JSDT bugzillas for planning purposes.
Nitin, you will probably deal with these problems with your UI work this milestone. Updated the target to m6.
This was fixed indirectly in M6 by https://bugs.eclipse.org/bugs/show_bug.cgi?id=274550. JS files still show up under WebContent even if that folder is added as a library or source folder. *** This bug has been marked as a duplicate of bug 274550 ***