Modular co-versioning in a dynamically linked runtime environment

• US 9,519,468 B2
• Filed: 02/13/2015
• Issued: 12/13/2016
• Est. Priority Date: 02/13/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Goetz, Brian, Sandoz, Paul D.
• Primary Examiner(s): TECKLU, ISAAC TUKU
• Application Number:
  US14/622,639
• Publication Number:
  US 20160239279A1
• Time in Patent Office: 669 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/54 Link editing before load time
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/44536 Selecting among different versions

Abstract

Modular co-versioning may involve the creation of multi-version libraries that may include multiple versions of a class. A multi-version library may include a base version and one or more other versions each of which may correspond to a particular, respective version of a software development kit, runtime environment or software platform, according to various embodiments. At runtime, a multi-version library may be searched in order to load a version of a class that corresponds to the version of the currently executing runtime environment. If the multi-version library does not include a version of the class corresponding to the currently executing version of the environment/platform, a version of the class corresponding to a previous version of the environment may be loaded if found in the multi-version library. Alternatively, if no other version of the class is found, a base version of the class may be loaded from the multi-version library.

Claims

1. A non-transitory, computer-readable storage medium storing program instructions that when executed on a computing device cause the computing device to perform:

loading, at runtime by a runtime module executing within a runtime environment, a class from a runtime linkable, multi-version library, wherein the multi-version library is configured to include multiple versions of classes, wherein all versions of a respective class correspond to an identical class signature for the respective class;

wherein said loading comprises;

determining whether the multi-version library includes a version of the class associated with a current version of a software development kit for implementing software executable within a respective current version of the runtime environment; and

in response to determining that the multi-version library does include the version of the class associated with the current version of the software development kit, loading, from the multi-version library, the version of the class associated with the current version of the software development kit.

2. The non-transitory, computer-readable storage medium of claim 1, wherein to load the version of the class associated with the current version of the software development kit, the program instructions further cause the computing device to perform:

loading the version of the class from a folder in the multi-version library associated with the current version of the software development kit, wherein the folder is configured to store versions of multiple classes, each associated with the current version of the software development kit.

3. The non-transitory, computer-readable storage medium of claim 1, wherein the program instructions further cause the computing device to perform:

in response to determining that the multi-version library does not include the version of the class associated with the current version of the software development kit;

determining whether the multi-version library comprises a version of the class associated with a specific previous version of the software development kit, wherein the specific previous version of the software development kit occurs prior than the current version of the software development kit in a defined order of software development kit versions; and

in response to determining that the multi-version library does include the version of the class associated with the specific previous version of the software development kit, loading, from the multi-version library, the version of the class associated with the specific previous version of the software development kit.

4. The non-transitory, computer-readable storage medium of claim 3, wherein the program instructions further cause the computing device to perform:

in response to determining that the multi-version library does not include the version of the class associated with the specific previous version of the software development kit, loading a base version of the class from the multi-version library, wherein the base version of the class is not associated with any particular version of the software development kit.

5. The non-transitory, computer-readable storage medium of claim 3, wherein to load, from the multi-version library, the version of the class associated with the specific previous version of the software development kit, the program instructions further cause the computing device to perform:

loading the version of the class associated with the specific previous version of the software development kit from a folder in the multi-version library associated with the specific previous version of the software development kit, wherein the folder is configured to store versions of multiple classes, each associated with the specific previous version of the software development kit.

6. The non-transitory, computer-readable storage medium of claim 1, wherein said determining whether the multi-version library includes a version of the class associated with a current version of a software development kit is performed without regard to the presence, within the multi-version library of a version of the class associated with a later version of the software development, wherein the later version of the software development kit occurs after the current version of the software development in a defined order of software development kit versions.

7. The non-transitory, computer-readable storage medium of claim 1, wherein the multi-version library is a multi-version archive implemented using a platform-independent, object oriented programming language.

8. A computing device, comprising:

a processor; and

a memory coupled to the processor, wherein the memory comprises program instructions that when executed by the processor, cause the processor to perform;

executing a class loader within a runtime environment;

loading, at runtime by the class loader, a class from a runtime linkable, multi-version library, wherein the multi-version library is configured to include multiple versions of classes, wherein all versions of a respective class correspond to an identical class signature for the respective class;

wherein said loading comprises;

determining whether the multi-version library includes a version of the class associated with a current version of a software development kit for implementing software executable within a respective current version of the runtime environment within which the class loader is executing; and

in response to determining that the multi-version library does include the version of the class associated with the current version of the software development kit, loading, from the multi-version library, the version of the class associated with the current version of the software development kit.

9. The computing device of claim 8, wherein to load the version of the class associated with the current version of the software development kit, the program instructions further cause the processor to perform:

loading the version of the class from a folder in the multi-version library associated with the current version of the software development kit, wherein the folder is configured to store versions of multiple classes, each associated with the current version of the software development kit.

10. The computing device of claim 8, wherein the program instructions further cause the processor to perform:

in response to determining that the multi-version library does not include the version of the class associated with the current version of the software development kit;

determining whether the multi-version library comprises a version of the class associated with a specific previous version of the software development kit, wherein the specific previous version of the software development kit occurs prior than the current version of the software development kit in an order to software development kit versions; and

in response to determining that the multi-version library does include the version of the class associated with the specific previous version of the software development kit, loading, from the multi-version library, the version of the class associated with the specific previous version of the software development kit.

11. The computing device of claim 10, wherein the program instructions further cause the processor to perform:

in response to determining that the multi-version library does not include the version of the class associated with the specific previous version of the software development kit, loading a base version of the class from the multi-version library, wherein the base version of the class is not associated with any particular version of the software development kit.

12. The computing device of claim 10, wherein to load, from the multi-version library, the version of the class associated with the specific previous version of the software development kit, the program instructions further cause the processor to perform:

loading the version of the class associated with the specific previous version of the software development kit from a folder in the multi-version library associated with the specific previous version of the software development kit, wherein the folder is configured to store versions of multiple classes, each associated with the specific previous version of the software development kit.

13. The computing device of claim 8,

wherein the respective current version of the runtime environment is associated with an earlier version of the software development kit as compared to a latest version of the software development kit in a defined order of software development kit versions;

wherein the multi-version library includes one or more versions of classes associated with the latest version of the software development kit; and

wherein said determining whether the multi-version library includes a version of the class associated with a current version of a software development kit comprises determining whether the multi-version library includes a version of the class associated with the earlier version of the software development kit and not determining whether the multi-version library includes a version of the class associated with the latest version of the software development kit.

14. The computing device of claim 8, wherein the multi-version library is a multi-version archive implemented using a platform-independent, object oriented programming language, and wherein said loading a class from the runtime linkable, multi-version library comprises a class loader executing on the computing device loading the class from the multi-version Java Archive.

15. A computer implemented method, comprising:

building, by a computing device comprising a hardware processor, a runtime linkable, multi-version library comprising multiple versions of a class, wherein the multiple versions all correspond to an identical class signature;

wherein said building comprises;

storing in the multi-version library a base version of the multiple versions of the class, wherein the base version of the class does not correspond to any particular version of a software development kit; and

storing in the multi-version library one or more other versions of the multiple versions of the class, wherein each of the one or more other versions correspond to respective versions of the software development kit.

16. The computer implemented method of claim 15, wherein said storing the one or more other versions of the class comprises storing metadata in the multi-version library indicating that each of the other versions corresponds to a respective version of the software development kit.

17. The computer implemented method of claim 15, wherein said storing the base version of the class comprises storing the base version of the class in a base folder of the multi-version library, wherein the folder is configured to store a respective base version of each of one or more classes, wherein the base folder does not correspond to any particular version of the software development kit.

18. The computer implemented method of claim 15, wherein said storing the one or more other versions of the class comprises storing each of the one or more other versions in respective folders of the multi-version library, wherein each respective folder is associated with a respective version of the software development kit.

19. The computer implemented method of claim 15, wherein the multi-version library is a multi-version archive implemented using a platform-independent, object oriented programming language.

20. The computer implemented method of claim 15, wherein the multi-version library is a dynamically linked library implemented using one or more of:

the C programming language;

the C++programming language;

or

the Java programming language.