Community
Participate
Working Groups
The equals in the ResourceNode is flawed in the sense that it uses the resource name for equality. Unfortunately, there are parts of Compare with Each ther that rely on this (see bug 157654). We should fix the equals and the Compare with Each Other action.
Verified in HEAD
Is this now for M2 or M3 as advertised in bug 157654 comment 7?
I think Bogdan closed this thinking it was bug 157654 was was fixed for M2. However, the proper fix has not been done (i.e. ResourceNode now has a flawed equals method and Compare with Each Other depends on this).
After some reflection, I've decided not to change the existing class because it is possible that existing clients rely on the flawed behavior. I've changed the title to indicate that we shoudl investigate whether file buffers should be used with Comapre with Each Other. However, we do not plan on addressing this in 3.3.
We are reworking Compare with Each Other in 3.4 at which point, we should be able to move back onto File Buffers.
*** Bug 181178 has been marked as a duplicate of this bug. ***
Mass update - removing 3.4 target. This was one of the bugs marked for investigation (and potential fixing) in 3.4 but we ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.