Community
Participate
Working Groups
1. For simplicity, consider a project with one class, Test, containing one method m1(). 2. Create a new branch. 3. In the branch, add a new method, Test.m2() 4. In the workspace following HEAD, try to bring m2() in - e.g., by merging (but it doesn't matter). 5. After hitting "copy from right to left" and saving, the method gets brought in two times.
should investigate for RC3
Approved for RC3 by Erich and Andre.
fixed and released for I20030314. Reviewed by Kai
The same problem occurs when merging Java properties. For the original bug we fixed the JavaNode, but we forgot to fix the parallel class PropertiesStructureCreator.
Erich and Dirk support to fix for RC3.
*** Bug 45528 has been marked as a duplicate of this bug. ***
Created attachment 12245 [details] patch for PropertiesStructureCreator
Created attachment 12246 [details] patch for PropertiesStructureCreator
reviewed with Martin and released for I20040616
start verifying...
Tested the following scenarios using build I200406192000: Scenario one: - messages.properties A.0= 0 A.1= 1 A.2= 2 - put into the reprository - deleted A.1= 1 - compare with HEAD - selected A1.1 - copied current change from right to left Scenario two: - properties file A.0= 0 A.2= 2 - created brach - in branch added A.1= 1 - released changes into branch - switched back to HEAD - merged changes with branch - copied current change from right to left In both cases only one occurrences of A.1= 1 got inserted.