Community
Participate
Working Groups
Since ICU4J provides more comprehensive support for internationalization and is now included as part of the Platform, we should be endorsing it by adopting use of its APIs instead of using the default Java implementation. One widespread example of usage that should be migrated to is using ICU's collator to sort in all of our viewers (see ViewerComparator) rather than the java.text collator used in ViewerSorter. This component was found to be affected by at least one of the 3 following conditions that should be adopted: 1. change references to java.text.Collator to com.ibm.icu.Collator. CAVEAT: There may be cases where this is not possible if plug-ins can ship without the com.ibm.icu plug-in (example, JFace). 2. change references to StructuredViewer#setSorter to use StructuredViewer#setComparator and StructuredViewer#getSorter to StructuredViewer#setComparator. These are slated to be deprecated (see bug 154871). 3. any classes that subclass ViewerSorter should now sublcass ViewerComparator, if possible (i.e. if the class is internal). The UI component is in the process of completing this work (see bug 154884) and it is slated to be released for M2.
JDT/Core does not use neither java.text.Collator nor StructuredViewer in org.eclipse.jdt.core project. However, we have one reference to java.text.Collator in one of our class in a test project: org.eclipse.jdt.core.tests.model.DefaultJavaElementComparator I'll change it...
Fixed and released for 3.3 M2
My bad - I saw a couple of jdt packages that didn't have "ui" in the name in my list of hits and assumed they were in the core plugin so that's why I logged a bug against JDT-Core. I suppose that changing the test suites is also a good idea. Thanks for catching that.
Verified for 3.3 M2 using build I20060918-0010.