Community
Participate
Working Groups
Build Identifier: 20100617-1415 The documentation states that comparing two files with identical content will result in a dialog indicating that the two files are the same. I remember this was correct with Version 2.x of Eclipse. The behaviour now is different: When comparing two files that are identical, a compare view is opened anyway, with both files shown and no differences marked. I suggest updating the docs to reflect the actual system behaviour. Reproducible: Always Steps to Reproduce: 1. Start Eclipse Helios (I use Eclipse IDE for Java EE) 2. On the Welcome page click "Overview", then "Workbench Basics" 3. Go to Getting Started->Basic Tutorial->Comparing->Simple Compare 4. There you are.
The dialog should come. This got broken during 3.5.
This looks like another regression introduced by bug 193324. Normally, when two files are the same, the compare editor input should return null as the computed compare result. This is no longer true for the SaveablesCompareEditorInput which returns a non-null result even though CompareEditors's state is NO_DIFF (checked here org.eclipse.compare.internal.CompareEditor.createCompareControl()). I'm setting this bug as another blocker to bug 275153, which gathers all regressions introduced by SaveablesCompareEditorInput.
See bug 315747, comment 9 for another case when the dialog should pop up.
We don't have the manpower to address it at this time. Need to postpone. Let us know, if you think it is important for 3.8 and you can help with it.
(In reply to comment #4) > We don't have the manpower to address it at this time. Need to postpone. Let us > know, if you think it is important for 3.8 and you can help with it. The master bug for the regressions (bug 275153) is targeted for 3.8 M7 and this one here is a blocker for said bug.
*** Bug 381082 has been marked as a duplicate of this bug. ***
Also affects the 4.2 release: Version: 4.2.0 Build id: I20120608-1400
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. If the bug is still relevant, please remove the stalebug whiteboard tag.
