SYNCHRONIZATION OF WORK SPACES

• US 20090019426A1
• Filed: 07/01/2008
• Published: 01/15/2009
• Est. Priority Date: 07/13/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gamma, Erich, Widmer, Tobias Kasper, Baeumer, Dirk
• Granted Patent: US 8,418,141 B2
• Time in Patent Office: Days
• US Class Current: 717/122
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/72 Code refactoring

Abstract

A method is provided for synchronization of a first workspace with a second workspace. Both workspaces are connected to a version control system. The method comprises for a first refactoring operation being performed on the first workspace, performing first refactoring step, resulting in a modification of an object, storing the modification in a change information for the object, storing in a change information recording step the change information, and storing in a descriptor recording step refactoring information comprising information enabling execution of a refactoring corresponding to the first refactoring step during an update operation. The method further comprises for a commit operation, delivering in a change information delivery step the change information to the version control system, and delivering in a descriptor commit step the refactoring information to the version control system. Then the method comprises for the update operation being performed on the second workspace, retrieving into the second workspace in a load step from the version control system the change information and the refactoring information, performing a second refactoring operation using the refactoring information, and performing in an execution step an update of the object in the second workspace using the change information.

Claims

1. A method for synchronization of a first workspace (W1) with a second workspace (W2), said workspaces (W1, W2) being connected to a version control system (V), the method comprising:

a. for a first refactoring operation (ROP1) being performed on said first workspace (W1),

i. performing a first refactoring step, resulting in a modification of an object (P1, F),

ii. storing the modification in a change information (C) for said object (P1, F),

iii. storing in a change information recording step said change information (C),

iv. storing in a descriptor recording step refactoring information comprising information enabling execution of a refactoring corresponding to said first refactoring step during an update operation (UOP),

b. for a commit operation (COP),

i. delivering in a change information delivery step said change information (C) to said version control system (V),

ii. delivering in a descriptor commit step said refactoring information to said version control system (V),

c. for said update operation (UOP) being performed on said second workspace (W2),

i. retrieving into said second workspace (W2) in a load step from said version control system (V) said change information (C) and said refactoring information,

ii. performing a second refactoring operation (ROP2) using said refactoring information,

iii. performing in an execution step an update of the object (P1, F) in said second workspace (W2) using said change information (C).

2. A method according to claim 1, wherein the descriptor recording step (24) is executed by a first refactoring engine module that is functional at said first workspace (W1).

3. A method according to claim 2, wherein the refactoring information is stored in a subfolder of a directory of said object (P1, F).

4. A method according to claim 3, wherein the refactoring information is stored as meta-data associated with the change information (C).

5. A method according to claim 4, wherein the change information (C) is presented to a first user (Ul) for deselection of items contained therein from being delivered in said change information delivery step.

6. A method according to claim 1, wherein the refactoring information is presented to a first user (U1) for deselection of items contained therein from being delivered in said descriptor commit step.

7. A method according claim 1, wherein the change information (C) is presented to a second user (U2) for deselection of items contained therein from being applied in said execution step.

8. A method according to claim 1, wherein the refactoring information is presented to a second user (U2) for deselection of items contained therein from being used in said second refactoring operation (ROP2).

9. A method according to claim 1, wherein other modifications of said object (P1, F) are also stored in said change information (C).

10. A method according to claim 1, wherein said second refactoring operation (ROP2) is performed before said execution step.

11. A method according to claim 1, wherein said change information delivery step is performed by a first VCS client that is functional at said first workspace (W1).

12. A method according to claim 1, wherein said descriptor commit step is performed by a first refactoring engine VCS extension that is functional at said first workspace (W1) and that is connected to said first VCS client and said first refactoring engine module.

13. A method according to claim 1, wherein said load step is performed by a second VCS client that is functional at said second workspace (W2).

14. A method according to claim 1, wherein the modifications created to the object (P1, F) by said second refactoring operation (ROP2) are overwritten by modifications to said object (P1, F) created by said execution step.

15. A method according to claim 1, wherein a second refactoring engine VCS extension is arranged at the second workspace (W2) to determine under use of the refactoring information pending refactoring for the object (P1, F) in said second workspace (W2) associated with the change information (C).

16. A method according to claim 15, wherein said second refactoring engine VCS extension is arranged for controlling the performance of said second refactoring operation (ROP2) and said execution step relative to each other.

17. A method according to claim 15, wherein said first refactoring engine VCS extension is arranged to also perform the functionality of the second refactoring engine VCS extension.

18. A method for synchronization of a first workspace (W1) with a second workspace (W2), said workspaces (W1, W2) being connected to a version control system (V), the method comprising at said first workspace (W1):

a. for a first refactoring operation (ROP1) being performed on said first workspace (W1),

i. performing a first refactoring step (11), resulting in a modification of an object (P1, F),

ii. storing the modification in a change information (C) for said object (P1, F),

iii. storing in a change information recording step said change information (C),

iv. storing in a descriptor recording step refactoring information comprising information enabling execution of a refactoring corresponding to said first refactoring step during an update operation (UOP),

b. for a commit operation (COP),

i. delivering in a change information delivery step said change information (C) to said version control system (V), for being retrievable into said second workspace (W2) to update said object (P1, F) therein,

ii. delivering in a descriptor commit step said refactoring information to said version control system (V), for being retrievable into said second workspace (W2) and usable for a second refactoring operation (ROP2).

19. A method according to claim 18, wherein the descriptor recording step is executed by a first refactoring engine module that is functional at said first workspace (W1).

20. A method according to any of claims 19, wherein the refactoring information is stored in a subfolder of a directory of said object (P1, F).

21. A method according to any of claims 18, wherein the refactoring information is stored as meta-data associated with the change information (C).

22. A method according to any of claims 18 wherein the change information (C) is presented to a first user (U1) for deselection of items contained therein from being delivered in said change information delivery step.

23. A method according to any of claims 18, wherein the refactoring information is presented to a first user (U1) for deselection of items contained therein from being delivered in said descriptor commit step.

24. A method according to any of claims 18, wherein other modifications of said object (P1, F) are also stored in said change information (C).

25. A method according to any of claims 18, wherein said second refactoring operation (ROP2) is performed before said execution step.

26. A method according to any of claims 18, wherein said change information delivery step is performed by a first VCS client that is functional at said first workspace (W1).

27. A method according to any of claims 18, wherein said descriptor commit step is performed by a first refactoring engine VCS extension that is functional at said first workspace (W1) and that is connected to said first VCS client and said first refactoring engine module.

30. A method according to any of claims 18, wherein the refactoring information is contained as meta-data associated with the change information (C).

31. A method according to any of claims 18, wherein the change information (C) is presented to a second user (U2) for deselection of items contained therein from being applied in said execution step.

32. A method according to any of claims 18, wherein the refactoring information is presented to a second user (U2) for deselection of items contained therein from being used in said second refactoring operation (ROP2).

34. A method according to any of claims 18, wherein said second refactoring operation (ROP2) is performed before said execution step.

35. A method according to any of claims 18, wherein said load step is performed by a second VCS client that is functional at said second workspace (W2).

36. A method according to any of claims 18, wherein modifications created to the object (P1, F) by said second refactoring operation (ROP2) are overwritten by modifications to said object (P1, F) created by said execution step (15).

37. A method according to any of claims 18, wherein a second refactoring engine VCS extension is arranged at the second workspace (W2) to determine under use of the refactoring information pending refactorings for the object (P1, F) in said second workspace (W2) associated with the change information (C).

39. A computer program element comprising computer program code means which, when loaded in a processor of a data processing system, configures the processor to perform a method according to any claim 18.

40. Computer program product comprising a computer-readable medium embodying program instructions executable by a processor to perform a method according to claim 18.

43. Second refactoring engine VCS extension according to claim 18, wherein said second refactoring engine VCS extension (75) is further adapted to control the execution of the pending refactorings by second refactoring operation (ROP2).

44. Second refactoring engine VCS extension according to claim 18, wherein said second refactoring engine VCS extension is further adapted to control the performance of an execution step by a second VCS client applying said change information (C).

28. A method for synchronization of a first workspace (W1), with a second workspace (W2), both workspaces (W1, W2) being connected to a version control system (V), the method comprising at said second workspace (W2):

a. for an update operation (UOP) being performed on said second workspace (W2),

i. retrieving into said second workspace (W2) in a load step from said version control system (V) change information (C) and refactoring information (40), wherein said change information (C) comprises a modification of an object (P1, F) that resulted from a first refactoring step (11) that was performed on said first workspace (W1), and said refactoring information comprises information enabling execution of a refactoring corresponding to said first refactoring step during said update operation (UOP),

ii. performing a second refactoring operation (ROP2) using said refactoring information,

iii. performing in an execution step an update of the object (P1, F) in said second workspace (W2) using said change information (C).

29. A method according to claim 28, wherein the refactoring information is contained in a subfolder of a directory of said object (P1, F).

33. A method according to any of claims 28, wherein other modifications of said object (P1, F) are also contained in said change information (C).

38. A method according to claim, wherein said second refactoring engine VCS extension is arranged for controlling the performance of said second refactoring operation (ROP2) and said execution step relative to each other.

41. First refactoring engine VCS extension being a part of a first workspace (W1), adapted to deliver in a descriptor commit step refactoring information to a version control system (V), for being retrievable into a second workspace (W2) and usable for a second refactoring operation (ROP2), wherein said refactoring information comprises information enabling execution of a refactoring corresponding to a first refactoring step during an update operation (UOP).

42. Second refactoring engine VCS extension being a part of a second workspace (W2), adapted to receive from a second VCS client refactoring information, wherein said refactoring information (40) comprises information enabling execution of a refactoring corresponding to a first refactoring step during an update operation (UOP) and to determine under use of said refactoring information pending refactorings for the object (P1, F) in said second workspace (W2) associated with a change information (C), wherein said change information (C) comprises a modification of an object (P1, F) that resulted from a first refactoring step that was performed on a first workspace (W1).