Community
Participate
Working Groups
Created attachment 122738 [details] Test case The two collectors used for finding locales in IUPropertyUtils short circuit if they don't find the item on the first try. For example, if you have 3 fragments that provide locales {A,B,C} and the one you want is in C, the current collector will check A, and simply short circuit if this is not the answer. The accept should return true if the item has not been found yet (remember, the return value of accept means: continue running the query). I have created a test case that demonstrates this problem.
Created attachment 122739 [details] Updated test (fixed a typo)
Created attachment 122740 [details] IUPropertyUtils fix This patch fixes the bug.
The patch looks like the right fix for the problem (obviously). My testing apparently didn't cover multiple localization fragments for a single iu.
is this waiting on anything else before it can be committed?
(In reply to comment #4) > is this waiting on anything else before it can be committed? > I think this is ready to go in (along with the test cases).
The fix should go in.
Patch released in HEAD.