Community
Participate
Working Groups
3.2RC7 With the latest Sun 1.5.0_08 VM, the implementation of HashMap seems to have changed, and iterating over the keys results in a different order. The JDT Core tests are now failing as they rely on the original order to compare the actual result against the expected result.
Created attachment 43972 [details] Proposed fix
Note that this fix changes the order of attributes in a classpath entry even if the VM doesn't change. There will be outgoing changes to the .classpath in the following scenario: 1. User runs Eclipse on Sun 1.4.2 VM. 2. This patch is applied 3. User adds a library entry to the build path User will see the the new entry as an outgoing change, BUT it will also see existing entries being changed since their attributes order has changed. There won't be any outgoing changes to the .classpath in the following scenario: 1. User runs Eclipse on Sun 1.4.2 VM. 2. This patch is applied 3. User edit the buildpath, adds a library in the buildpath wizard, changes her mind and remove the library, then press OK.
Released in HEAD. Released in TARGET_321.
Released for 3.2.1 Released for 3.3 M1
Verified for 3.3 M1 using build I20060807-0010.