Method and apparatus for upgrading a software application in the presence of user modifications

• US 7,076,778 B2
• Filed: 02/22/2002
• Issued: 07/11/2006
• Est. Priority Date: 02/27/1997
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Hastings, Mark C, Coker, John L., Brodersen, Robert S.
• Primary Examiner(s): Vo, Ted T.
• Application Number:
  US10/079,499
• Publication Number:
  US 20020129352A1
• Time in Patent Office: 1,600 Days
• Field of Search: 717104-123, 717168-173
• US Class Current: 717/170
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

A method for upgrading (31-b of FIG. 1) a software application (35-b) from a prior version to a subsequent version while preserving user modifications to the prior application. The method includes comparing differences between the two versions of the software applications. This is followed by enumerating the differences between the two versions of the software applications; and determining which differences between the two versions of the software are conflicting and which are compatible. The compatible changes are made (7). Also disclosed is an article of manufacture containing computer readable program code for carrying out the above process, and a program storage device carrying the code.

Claims

1. A computer-implemented method of upgrading a software application by merging two modified versions of a common ancestor version, the method comprising:

receiving indications of a first modified version of the common ancestor version and of a distinct second modified version of the common ancestor version; and

without user intervention, automatically creating a new version of the software application by merging the first and second modified versions, by

automatically collecting object definitions from an ancestor repository associated with the common ancestor version, from a first repository associated with the first modified version, and from a second repository associated with the second modified version;

identifying a first set of modified objects in the first modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

identifying a second set of modified objects in the second modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

determining which of the identified modified objects in the first set of modified objects are compatible with the second modified version; and

creating the new version of the software application by merging the compatible modified objects with the second modified version.

2. The computer-implemented method of claim 1 further comprising determining which of the identified modified objects in the first set of modified objects are conflicting modified objects with the second modified version.

3. The computer-implemented method of claim 2, further comprising:

automatically notifying a user of the conflicting modified objects; and

presenting options to the user for resolving the conflicting modified objects.

4. The computer-implemented method of claim 2 including automatically resolving one or more of the conflicting modified objects without user intervention based at least in part on predefined conflict resolution rules, and wherein the automatic determining of the compatible modified objects includes selecting the resolved conflicting modified objects.

5. The computer-implemented method of claim 3 including determining an importance of each of one or more of the conflicting modified objects, and wherein the notifying of the user of conflicting modified objects includes providing notification of the determined importances.

6. The computer-implemented method of claim 1 wherein the modified objects determined to be compatible include conflicting modified objects that are identified as superficial.

7. The computer-implemented method of claim 1 wherein the modified objects determined to be compatible include conflicting modified objects identified as being of high priority.

8. The computer-implemented method of claim 1 including, before identifying the first set of modified objects and the second set of modified objects, displaying to a user a graphical user interface related to creating the new version of the software application, and wherein the identifying the first set of modified objects and the second set of modified objects is in response to an indication from the user via the graphical user interface.

9. The computer-implemented method of claim 8 wherein the displaying of the graphical user interface to the user includes displaying an option to include differences between the first and second modified versions only if the differences correspond to high priority aspects of the first and second modified versions and/or displaying an option to abort creating the new version if a specified number of errors is exceeded.

10. The computer-implemented method of claim 8 wherein one of the modified versions has been customized by the user so as to delete one or more aspects of the common ancestor version, wherein the aspects of the common ancestor version deleted in the one modified version have not been deleted in the other modified version, and including displaying an option to the user to select the deleted aspects as being a compatible difference such that the created new version does not include the deleted aspects.

11. The computer-implemented method of claim 1 including displaying to a user at least some of the differences between each of the two modified versions and the common ancestor version so as to allow visual comparison of those two modified versions.

12. The computer-implemented method of claim 1 wherein at least one of the modified versions includes modifications made by a user and/or at least one of the modified versions includes modifications made by a developer of the software application.

13. The computer-implemented method of claim 1 wherein the first modified version includes user modifications to a prior version of the software application, wherein the second modified version is an upgrade for that prior version, and wherein the creating of the new version is to upgrade the software application to a version of the upgrade that includes at least some of the user modifications.

14. The computer-implemented method of claim 13, wherein the user-modified prior version comprises a first plurality of objects and the prior version comprises a third plurality of objects and the upgrade version comprises a second plurality of objects, and wherein the determining of the first and second sets of modified objects comprises:

determining one or more objects from the first plurality of objects that share a common name with one or more objects from the third plurality of objects;

for each of at least one of the objects from the first plurality of objects that shares a common name with one of the objects from the third plurality of objects, determining one or more attributes associated with that object that differs from the attributes associated with the object that shares the common name and including data related to the difference between those attributes in the first set of modified objects;

determining one or more objects from the second plurality of objects that share a common name with one or more objects from the third plurality of objects; and

for each of at least one of the objects from the second plurality of objects that shares a common name with one of the objects from the third plurality of objects, determining one or more attributes associated with that object that differs from the attributes associated with the object that shares the common name and including data related to the difference between those attributes in the second set of modified objects.

15. The computer-implemented method of claim 13 wherein the user-modified prior version comprises a first plurality of objects, the prior version comprises a third plurality of objects, and the upgrade version comprises a second plurality of objects, and wherein the determining of the modified objects comprises determining that an object from the first plurality of objects is not included within the second or third plurality of objects and indicating that that object is a compatible modified object.

16. The computer-implemented method of claim 13 wherein the user-modified prior version comprises a first plurality of objects, the prior version comprises a third plurality of objects, and the upgrade version comprises a second plurality of objects, and wherein the determining of the set of differences comprises determining that an object from the second and third plurality of objects is not included within the first plurality of objects and indicating that absence of that object from the first plurality of objects is a conflicting modified object.

17. A computer-readable medium whose contents cause a computing device to perform a method for upgrading at least portions of a modified version of a software application based at least in part on another distinct modified version of the software application, the method comprising:

automatically collecting object definitions from an ancestor repository associated with the common ancestor version, from a first repository associated with the first modified version, and from a second repository associated with the second modified version;

identifying a first set modified objects in the first modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

identifying a second set of modified objects in the second modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

determining which of the identified modified objects in the first set of modified objects are compatible with the second modified version; and

creating the new version of the software application by merging the compatible modified objects with the second modified version.

18. The computer-readable medium of claim 17 wherein the portions of the first modified version that differ from the portions of the second modified version are objects associated with the first modified version that differ from objects associated with the second modified version.

19. The computer-readable medium of claim 17 wherein the contents that cause the computing device to perform the method is executable software code.

20. An apparatus for upgrading a software application from a user-modified prior version to an upgrade version, the user-modified prior version and the upgrade version having a common ancestor version, the apparatus comprising:

a first component able to automatically collect object definitions from an ancestor repository associated with the common ancestor version, from a first repository associated with the first modified version, and from a second repository associated with the second modified version;

a second component able to identify a first set modified objects in the first modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions and to identify a second set of modified objects in the second modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

a third component able to determine which of the identified modified objects in the first set of modified objects are compatible with the second modified version; and

a fourth component able to create the new version of the software application by merging the compatible modified objects with the second modified version.

21. A computing device for upgrading a software application from a user-modified prior version to an upgrade version, wherein the user modified prior version and the upgrade version have a common ancestor version, said apparatus comprising:

means for automatically collecting object definitions from an ancestor repository associated with the common ancestor version, from a first repository associated with the first modified version, and from a second repository associated with the second modified version;

means for identifying a first set modified objects in the first modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

means for identifying a second set of modified objects in the second modified version by comparing against attributes of corresponding objects in the common ancestor version based on the object definitions;

means for determining which of the identified modified objects in the first set of modified objects are compatible with the second modified version; and

means for creating the new version of the software application by merging the compatible modified objects with the second modified version.