Community
Participate
Working Groups
In 1.5, if I have a web project A that includes another web project B in its build path, the internal project information for each one contains a complete set of records for taglibs found in the build path for B, once when A indexes B and then again if B is indexed by itself. The time spent initially searching a project's build path is not insignificant, so this information needs to be reorganized to reduce the time spent indexing and the amount of memory it uses.
Created attachment 49532 [details] proposed patch Attaching a patch that allows individual project descriptions to ask each other about tag libraries on their build path.
Chuck, could you retry your import scenario with the attached patch?
Reviewed and tested.... Solves my large workspace scenario....
Created attachment 49869 [details] updated patch Updated to fix a problem with remembering required projects on the build path in between sessions that was found while fleshing out the unit tests.
+1
+1 for WTP 1.5.1
Fixed
Verified in 1.5.1. Closing.