System and method for providing a java code release infrastructure with granular code patching

• US 7,127,712 B1
• Filed: 02/11/2002
• Issued: 10/24/2006
• Est. Priority Date: 02/14/2001
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Epstein, Joseph, Greene, William, Lotero, Richard J., Noble, Kenton E., Swartz, Keith, Kent, Joseph H., Chadalavada, Subash
• Primary Examiner(s): STEELMAN, MARY J
• Application Number:
  US10/073,669
• Time in Patent Office: 1,716 Days
• Field of Search: 717/173, 717/169, 717/168
• US Class Current: 717/173
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A system and method for providing a code release infrastructure with granular code patching is described. Code patches, each including at least one resource unit are provided. Each resource unit includes metadata and file components. Code libraries, each including at least one resource unit, are patched. The metadata for each resource unit in the code patches is compared to the metadata for each such corresponding resource unit in the code libraries. Each resource unit in the code patches is merged into the code libraries for each such corresponding resource unit that is out-of-date as defined by merge rules. Archive files, as defined by archive file definitions, are created or updated using the resource units from the code libraries, or, optionally, are deleted. The archive files are digitally signed also as required. The system and method enables source and derived code and third party code to be patched granularly.

Claims

1. A system for providing a JAVA code release infrastructure with granular code patching, comprising:

a computer readable storage medium holding one or more JAVA code patches, each comprising at least one resource unit, each resource unit comprising metadata and file components;

a computer readable storage medium holding one or more to-be-patched JAVA code libraries, each comprising at least one such resource unit;

a computer readable storage medium holding a patch tool, comprising;

a compare module that determines which units in the to-be-patched JAVA code libraries are outdated by comparing the metadata for each such resource unit in the JAVA code patches to the metadata for each such corresponding resource unit in the to-be-patched JAVA code libraries; and

a merge module merging each such resource unit in the JAVA code patches into the to-be-patched JAVA code libraries for each such corresponding resource unit that is out-of-date.

2. A system according to claim 1, further comprising:

an extract module extracting at least one resource unit from the JAVA code libraries and modifying one or more JAVA archive files that are out-of-date with the at least one extracted resource unit.

3. A system according to claim 1, further comprising:

a sign module signing the JAVA archive files using a digital certificate.

4. A system according to claim 1, wherein the one or more JAVA archive files are modified through at least one of creation, revision or deletion.

5. A system according to claim 1, further comprising:

a source repository storing the source file components;

a staged patch repository storing the one or more JAVA code patches; and

a staged code repository organizing the one or more JAVA code libraries and the JAVA archive files.

6. A system according to claim 1, further comprising:

a resource unit generator processing the file components into at least one such resource unit; and

a packager packaging at least one such resource unit into one or more of the JAVA code patches.

7. A system according to claim 6, further comprising:

stored JAVA source code provided as the file components.

8. A system according to claim 7, further comprising:

a compiler compiling at least one JAVA source code file into one or more JAVA classes; and

a resource unit packager module storing the JAVA classes into at least one such resource unit as the file components.

9. A system according to claim 6, further comprising:

at least one of non-JAVA source and derived code provided as the file components.

10. A system according to claim 6, further comprising:

third party code provided as the file components.

11. A system according to claim 6, further comprising:

a metadata generator generating the metadata for each such resource unit; and

a resource unit packager module storing the generated metadata into the resource unit.

12. A system according to claim 11, wherein the metadata comprises at least one of a unique identifier and a version attribute.

13. A system according to claim 1, further comprising:

a compare module using a set of rules allowing one of an older resource unit to be replaced by a newer resource unit and a newer resource unit to be replaced by an older resource unit to back out a previously-applied JAVA code patch.

14. A system according to claim 1, further comprising:

one or more JAVA archive files, each comprising at least one resource unit corresponding to one such resource unit in the JAVA code libraries; and

a patch tool referencing JAVA archive file definitions which each correspond to one or more of the JAVA archive files.

15. A system according to claim 14, further comprising:

an extract module extracting the resource units from the JAVA code libraries into the JAVA archive files for each such corresponding resource unit that is out-of-date.

16. A system according to claim 15, further comprising:

an extract module referencing third party JAVA code libraries not maintained as part of the infrastructure.

17. A system according to claim 1, further comprising:

JAVA code libraries implemented as a portable virtual file system which can be used directly by a JAVA Virtual Machine.

18. A system according to claim 1, further comprising:

a machine portable infrastructure providing support for JAVA language features by encapsulating JAVA inner classes, nested directory structures, native class names, and native character set.

19. The system of claim 1, wherein the compare module resides on a client machine that is separate from a server machine on which resides a patch generator that generated the one or more JAVA code patches.

20. The system of claim 19, wherein the client machine downloads the one or more JAVA code patches from the server machine.

21. A method for providing a JAVA code release infrastructure with granular code patching, comprising:

providing one or more JAVA code patches, each comprising at least one resource unit, each resource unit comprising metadata and file components;

patching one or more to-be-patched JAVA code libraries, each comprising at least one such resource unit;

comparing the metadata for each such resource unit in the JAVA code patches to the metadata for each such corresponding resource unit in the to-be-patched JAVA code libraries; and

merging each such resource unit in the JAVA code patches into the to-be-patched JAVA code libraries for each such corresponding resource unit that is out-of-date.

22. A method according to claim 21, further comprising:

extracting at least one resource unit from the JAVA code libraries and modifying one or more JAVA archive files that are out-of-date with the at least one extracted resource unit.

23. A method according to claim 21, further comprising:

signing the JAVA archive files using a digital certificate.

24. A method according to claim 21, wherein the one or more JAVA archive files are modified through at least one of creating, updating or deleting.

25. A method according to claim 21, further comprising:

storing source file components into a source repository;

storing one or more JAVA code patches into a staged patch repository; and

organizing one or more JAVA code libraries and the JAVA archive files into a staged code repository.

26. A method according to claim 21, further comprising:

processing the file components into at least one such resource unit; and

packaging at least one such resource unit into one or more of the JAVA code patches.

27. A method according to claim 26, further comprising:

providing JAVA source code as the file components.

28. A method according to claim 25, further comprising:

compiling at least one JAVA source code file into one or more JAVA classes; and

storing the JAVA classes into at least one such resource unit as the file components.

29. A method according to claim 26, further comprising:

providing at least one of non-JAVA source and derived code as the file components.

30. A method according to claim 26, further comprising:

providing third party code as the file components.

31. A method according to claim 26, further comprising:

generating the metadata for each such resource unit; and

storing the generated metadata into the resource unit.

32. A method according to claim 31, wherein the metadata comprises at least one of a unique identifier and a version attribute.

33. A method according to claim 21, further comprising:

using a set of rules to allow one of an older resource unit to be replaced by a newer resource unit and a newer resource unit to be replaced by an older 3 resource unit to back out a previously-applied JAVA code patch.

34. A method according to claim 21, further comprising:

providing one or more JAVA archive files, each comprising at least one resource unit corresponding to one such resource unit in the JAVA code libraries; and

referencing JAVA archive file definitions which each correspond to one or more of the JAVA archive files.

35. A method according to claim 34, further comprising:

extracting the resource units from the JAVA code libraries for each such corresponding resource unit that is out-of-date.

36. A method according to claim 35, further comprising:

referencing third party JAVA code libraries not maintained as part of the infrastructure.

37. A method according to claim 21, further comprising:

implementing JAVA code libraries as a portable virtual file system which can be used directly by a JAVA Virtual Machine.

38. A method according to claim 21, further comprising:

providing a machine portable infrastructure supporting JAVA language features by encapsulating JAVA inner classes, nested directory structures, native class names, and native character set.

39. A computer-readable storage medium holding code for performing the method of claim 21.

40. The method of claim 21, wherein the step of comparing is performed on a client machine that is separate from a server machine on which resides a patch generator that generated the one or more JAVA code patches.

41. The method of claim 40, further comprising downloading the one or more JAVA code patches from the server machine to the client machine.

42. A system for patching staged code in a staged JAVA code release infrastructure, comprising:

a staged code repository maintaining one or more staged to-be-patched JAVA code libraries, each staged to-be-patched JAVA code library comprising at least one resource unit, each resource unit comprising metadata and file components;

a staged patch repository storing one or more JAVA code patches, each JAVA code patch comprising at least one resource unit corresponding to one such resource unit specified in a JAVA code patch definition; and

a patch tool accessing one or more JAVA code patches in the staged patch repository, comprising;

a compare module comparing the metadata for each resource unit in the JAVA code patches to the metadata in the staged to-be-patched JAVA code libraries for each such corresponding resource unit; and

a merge module merging each resource unit in the JAVA code patches into the staged to-be-patched JAVA code libraries for each such corresponding resource unit that is out-of-date.

43. A system according to claim 42, further comprising:

an extract module referencing JAVA archive file definitions which each correspond to a staged JAVA archive file, each staged JAVA archive file comprising at least one resource unit corresponding to one such resource unit in the staged JAVA code libraries.

44. A system according to claim 43, further comprising:

an extract module extracting one such resource unit from the staged JAVA code libraries into the staged JAVA archive files for each such corresponding resource unit that is out-of-date.

45. A system according to claim 44, further comprising:

a sign module creating a digital signature for the staged JAVA archive files using a digital certificate.

46. The system of claim 42, wherein the compare module resides on a client machine that is separate from a server machine on which resides a patch generator that generated the JAVA code patches.

47. A method for patching staged code in a JAVA code release infrastructure, comprising:

maintaining one or more staged to-be-patched JAVA code libraries in a staged code repository, each staged to-be-patched JAVA code library comprising at least one resource unit, each resource unit comprising metadata and file components;

accessing one or more JAVA code patches in a staged patch repository, each JAVA code patch comprising at least one resource unit corresponding to one such resource unit specified in a JAVA code patch definition;

comparing the metadata for each resource unit in the JAVA code patches to the metadata in the staged to-be-patched JAVA code libraries for each such corresponding resource unit; and

merging each resource unit in the JAVA code patches into the staged to-be-patched JAVA code libraries for each such corresponding resource unit that is out-of-date.

48. A method according to claim 47, further comprising:

referencing JAVA archive file definitions which each correspond to a staged JAVA archive file, each staged JAVA archive file comprising at least one resource unit corresponding to one such resource unit in the staged JAVA code libraries.

49. A method according to claim 48, further comprising:

extracting one such resource unit from the staged JAVA code libraries into the staged JAVA archive files for each such corresponding resource unit that is out-of-date.

50. A method according to claim 49, further comprising:

creating a digital signature for the staged JAVA archive files using a digital certificate.

51. A computer-readable storage medium holding code for performing the method of claim 47.

52. The method of claim 47, wherein the step of comparing is performed on a client machine that is separate from a server machine on which resides a patch generator that generated the JAVA code patches.

53. A computer-implemented method for patching code, the method comprising:

downloading, to a client machine, from a server machine that is separate from the client machine, one or more patches that were generated on the server machine;

comparing, at the client machine, (a) contents of the one or more patches to (b) code that is not resident on the server machine;

based on the comparing, determining one or more out-of-date portions within the code; and

applying at least a part of the one or more patches to the out-of-date portions without applying any part of the one or more patches to parts of the code other than the out-of-date portions.