Community
Participate
Working Groups
We plan to fix the warnings during the next milestones. So far I'm fixing warnings in the official build.
(In reply to comment #0) > So far I'm fixing warnings in the official build. To clarify, I just used javacWarnings.<jar>=-raw,-unchecked to ignore these warnings in the build.
Part of the work was already done during M5. We will continue in M6.
Created attachment 188035 [details] patch 1 I've squashed the bulk of these warnings core.resources, including generic-izing most of the internal collections. Attached patch committed.
(In reply to comment #3) > Created attachment 188035 [details] > patch 1 > > I've squashed the bulk of these warnings core.resources, including > generic-izing most of the internal collections. > Attached patch committed. Could we wait with such changes till IBuild is run and finished next time?
Created attachment 188039 [details] New problems in my workspace I'm on M5. I've just donwloaded core.tests.resources from the repo and see new problems. James, do you see it too?
(In reply to comment #5) > Created attachment 188039 [details] > New problems in my workspace > > I'm on M5. I've just donwloaded core.tests.resources from the repo and see new > problems. James, do you see it too? False alarm. I synced again and the errors disappeared.
It is partially fixed. I'll try to look at it during RCs.
I handled core.resources thanks to Markus' hints. I do not plan to make a pass for core.tests.resoures. I hope to see them updated while fixing bugs or adding new tests etc.