Community
Participate
Working Groups
Follow-up from bug 522326 It is not clear, whether our current solution will always derive the correct solution in convoluted cases of multiple same-named types from different modules, participating in different SplitPackageBindings and entering compilation as UnresolvedReferenceBinding. See bug 522326 comment 10 for analysis so far.
Bulk move out of 4.9
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.