Community
Participate
Working Groups
STEPS: WHen I do multiple consecutive Replace With -> Local History operations, more "editions" (timestamps) are created in the local history, even though I didn't make any changes and save them in the interim. *In a java project in the Resource perspective, create a new file named Moo.java. *In the Moo.java editor paste the following and save: public class Moo { private int y; public Moo() { } public void doThis() { } abstract public void doThat(); public int getX() { return x; } } At this point there should be two versions visible in the local history, one with an empty class def, and one with the class def shown above. *In the text editor, delete the following line and then save: abstract public void doThat(); Now there are 3 versions in the local history. *In Nav, select the file and do Replace with -> Local History Select the previous version. I think this is when the extra version gets created but you will not see this until after the next step. *Do another Replace with -> Local History Select the top version. BUG: Now Select Replace with -> Local history and look at the number of versions in the list - it has increased by one! The top 2 versions are the same code. I haven't saved anything new since I started doing the Replace with operations. If you keep doing 'Replace with -> Local History', you get a new version after every second 'Replace with' you do. NOTES: KM (09/17/01 2:29:51 PM) Moving to ITPUI.
PRODUCT VERSION: eclipse sdk 135 winnt 4.0
Defer
Still occurs. Reopen for investigation.
Moving to Core for comments
I believe that what is being asked is that file contents should not be stored in local history if they already exist there. Unfortuanatly we do not know whether or not a file's contents were retrieved from local history or some other means. Potentially we (core, the editor, compare, etc) could try and keep track of this kind of information but it would be very easy for this information to become out of sync with the actual contents of the local history since the local history can be flushed/pruned at any point in time based on a number of different policy settings. Closing as WONTFIX.