Community
Participate
Working Groups
bug 146015 follow-up TypeHierarchyTests.testRegion4() fails if this test suite is run using -Dordering=700 VM argument. Problem comes from the fact that with this specific order, jclMin.jar belongs sometimes to "TypeHierarchy" project instead of always belonging to "P1" project while running with default order. I haven't found the reason of this difference, but the side effect is that while pruning dead branches of hierarchy, class files of jclMin.jar which belongs to "TypeHierarchy" project are removed because none of their ancestors matches region projects (ie. Region.contains(IJavaElement) returns false for these class files).
FYI: It also fails running with -Dordering=670
Created attachment 44390 [details] Proposed fix
Fix seems like it should be extended to handle internal JAR from other projects as well (ie. all jar pkg fragment roots)
Created attachment 44391 [details] Improved fix
Patch released for 3.3M1 in HEAD.
Patch released for 3.2.1 in TARGET_321 branch.
Verified for 3.3 M1 using build I20060807-0010.
Verified for 3.2.1 using build M20060908-1655