Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341449

Summary: Folder comparison modifications on translation unit cannot be saved
Product: [Eclipse Project] Platform Reporter: Paul Chan <pchan>
Component: CompareAssignee: Platform-Compare-Inbox <platform-compare-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: pchan
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Screenshot on the folder compare
none
Sample project for illustrating the problem none

Description Paul Chan CLA 2011-03-31 03:36:26 EDT 
Build Identifier: 20110317-0634

When comparing 2 folders using Eclipse build-in compare, modifications on the same translation unit cannot be saved:
The '*' appears in the title when the translation unit was modified, but it disappears in few seconds. The modifications cannot be saved.

If comparing the same file, by selecting 2 files instead of 2 folders, the '*' appears normally when the translation unit was modified, can modifications can be saved.


Reproducible: Always

Steps to Reproduce:
1. With the sample project test attached, select "src1" and "src2", right click and then Compare With->Each other
2. When the comparing editor appears, double click the translation unit: the C structure "s"
3. Try to modify anything of the structure, and the problem can be observed.
Comment 1 Paul Chan CLA 2011-03-31 03:39:45 EDT 
Created attachment 192252 [details]
Screenshot on the folder compare
Comment 2 Paul Chan CLA 2011-03-31 03:40:51 EDT 
Created attachment 192253 [details]
Sample project for illustrating the problem
Comment 3 Lars Vogel CLA 2019-11-08 04:39:38 EST 
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.