Community
Participate
Working Groups
Build Identifier: I20100305-1011 This bug is to track the following issues. 1. Investigate if JavaModelManager#getNonChainingJarsCache() should store the nonChainingJars in the instance variable. 2. In JavaModelManager#getNonChainingJarsCache(), Collections.synchronizedSet() could be used at the end of the function before returning! This will avoid some unnecessary synchronization of the local hashset. Reproducible: Didn't try
Created attachment 162789 [details] Proposed Patch Patch with tests Satyam, can you review this, please? One note about the change to JavaModelManager#getNonChainingJarsCache: The check to return the existing this.nonChainingJars ensures that non chaining jars cache is computed again only right after a reset. Even if there is one entry we save the cache as is.
Jay, Things does not look good if they are two projects. The second project is overwriting the nonchained jars for the first one. Can you look at that?
+1 for the proposed patch. Though the attached test fails if expanded to two projects, it should not impact the correctness.
Released in HEAD for 3.6M7.
Verified for 3.6M7 through code inspection
Verified.