Community
Participate
Working Groups
Build ID: 3.3.0 - I20070222-0951 Steps To Reproduce: 1.Create a dynamic web project 2.Create a Java project 3.Make the web project depend on the Java project (add it to the "J2EE module dependencies" 4.Refactor the Java project and change its name 5.The web project cannot be compiled, because it is looking for a "missing required Java project" (it is looking for a project with the old name) More information: using WTP 2.0 M5
Well, this is not an issue with the refactoring logic, that is working fine (the dependent-module element for the dependent Java project is correctly updated to have the new name); if you close and reopen web project, everything is happy; so, looks like an issue with refreshing the web app libraries cp container (either in the virtual comp layer or the cp container impl) - going to debug more into it now and will update and possibly reassign as appropriate.
hmmm, the WebAppLibrariesContainer appears to be updating things correctly - nothing interesting in the log
OK, something interesting: disabling resolution of cp entry-based virtual references appears to fully eliminate this issue; so, there is some bad interaction between that logic and the cp container refresh
False lead - the issue is sporadic
Here is the latest: -It is sporadic -When I debug into WebAppLibrariesContainer.refresh(), everything looks OK in terms of the new cp entries that are created based on the computed virtual references -I've been able to get this to repro with virtual reference computation for cp entries commented out so I believe that is not involved. -I've been able to get this to repro by just renaming a jar file under the WEB-INF/lib folder so project rename/delete refactoring is not involved. So, looks like our mechanism of triggering a container refresh/reinstall via a resource change listener (FlexibleProjectContainer.Listener) is no longer working for some reason (likely due to an underlying change in 3.3); Konstantin, looks like listener (and base container class) has been primarily your code so sending you way next. Let me know if you think the classpath dependency logic looks in any way involved here.
Can someone from the JDT team take a look at this repro? I suspect there might be a race condition between the part of the JDT that's in charge of producing this error and the part that's responsible for managing the actual classpath. To repro, you can do the following: 1. Get an M6 build of WTP and the dependencies. 2. Import the attached projects (will attach in a sec). 3. Setup your workbench so that you can see Project Explorer, Navigator, and Problems views at the same time. 4. In the Project Explorer view, expand the Web App Libraries classpath container. Note that it has a single jar in it. This classpath container is responsible for putting jars in web app's WEB-INF/lib directory on the project classpath. 5. Find this jar in the Navigator view (WebContent/WEB-INF/lib/stuff.jar). 6. Rename it. 7. You should see the Web App Libraries container in the Project Explorer view update to reflect the new name of the jar. 8. Did you get "Project 'web' is missing required library: 'WebContent/WEB-INF/lib/stuff.jar'" error message in the problems view? If not, repeat steps 6-8. I get this to repro with approx 50% consistency. 9. Once you get into this state, cleaning the project doesn't help, but closing and re-opening it does help. Reducing the severity since the problem doesn't happen all the time and when it does there is a work-around (close and re-open the project).
Created attachment 64116 [details] Repro Project
Created attachment 67197 [details] Possible fix and regression test
Created attachment 67203 [details] Possible fix and improved regression test
Fix and test released for 3.3RC1 in HEAD.
Verified for 3.3 RC1 using I20070516-0010
