Synthesized modules for module renaming

• US 10,346,225 B2
• Filed: 09/14/2017
• Issued: 07/09/2019
• Est. Priority Date: 09/14/2017
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Buckley, Alexander R., Bateman, Alan
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US15/704,156
• Publication Number:
  US 20190079811A1
• Time in Patent Office: 663 Days
• Field of Search: 717162-178
• CPC Class Codes: G06F 2209/463 Naming
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45525 Optimisation or modification within the same instruction set architecture, e.g. HP Dynamo
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Techniques for renaming a module in a module system are disclosed. It is determined that a first module is declared with a corresponding first module name. It is determined that the first module is associated with a second module name. Responsive to determining that the first module is associated with the second module name: a second module declared with the second module name is synthesized, and a dependency of the second module, with the second module name, is declared on the first module with the first module name.

Claims

1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

determining that a first module is declared with a corresponding first module name;

determining that the first module, with the corresponding first module name, is also associated with a second module name;

responsive to determining that the first module is associated with the second module name;

synthesizing a second module declared with the second module name;

defining a first dependency of the second module, with the second module name, on the first module with the first module name,

wherein the first dependency of the second module is a transitive dependency based on a determination that the first module exposes an application programming interface (API).

2. The medium of claim 1, wherein determining that the first module is associated with the second module name is based on identification of the second module name in a source code in which the first module is declared.

3. The medium of claim 1, wherein determining that the first module is associated with the second module name is based on identification of the second module name in a module descriptor of the first module.

4. The medium of claim 1, wherein determining that the first module is associated with the second module name is based on a response to a query for a module name history associated with the corresponding first module name, the response comprising the second module name.

5. The medium of claim 1, wherein determining that the first module is associated with the second module name comprises determining that the first module was declared with the second module name prior to a modification in which the first module was declared with the first module name.

6. The medium of claim 1, wherein synthesizing the second module is performed only if any other module includes a second dependency comprising the second module name.

7. The medium of claim 1, the operations further comprising:

detecting addition, at runtime, of a third module that includes a second dependency comprising the second module name,

wherein synthesizing the second module is performed further responsive to detecting addition of the third module.

8. The medium of claim 1, the operations further comprising:

detecting that a third module includes a second dependency comprising the second module name; and

allowing, based on the first dependency of the second module and the second dependency of the third module, the third module to access types from the first module.

9. The medium of claim 1, the operations further comprising:

detecting that a third module includes a second dependency comprising the corresponding first module name; and

allowing, based on the second dependency of the third module, the third module to access types from the first module.

10. The medium of claim 1, wherein the second module does not expose any elements of its own and does not include any dependencies other than the first dependency.

11. The medium of claim 1, the operations further comprising:

generating an error in response to determining that a third module is declared with a second module name that is identical to the second module name associated with the first module.

12. The medium of claim 1, the operations further comprising:

generating an error in response to determining that the second module name associated with the first module is identical to a second module name declared for a third module.

13. The medium of claim 1, wherein synthesizing the second module is performed in response to determining, at runtime, that the first module is associated with the second module name.

14. The medium of claim 1, the operations further comprising:

associating, at runtime prior to synthesizing the second module, the first module with the second module name.

15. The medium of claim 1, wherein synthesizing the second module is performed during a compilation process in response to determining, during the compilation process, that the first module is associated with the second module name.

16. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

determining that a first module is declared with a corresponding first module name;

determining that the first module, with the corresponding first module name, is also associated with a second module name;

responsive to determining that the first module is associated with the second module name;

synthesizing a second module declared with the second module name;

defining a first dependency of the second module, with the second module name, on the first module with the first module name,

wherein synthesizing the second module comprises;

identifying metadata associated with the first module and applicable to the first module; and

associating the metadata with the second module to make the metadata applicable to the second module.

17. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

determining that a first module is declared with a corresponding first module name;

determining that the first module, with the corresponding first module name, is also associated with a second module name;

responsive to determining that the first module is associated with the second module name;

synthesizing a second module declared with the second module name;

defining a first dependency of the second module, with the second module name, on the first module with the first module name;

determining, based on metadata associated with the second module, that one or more of the first module and the second module is deprecated.

18. A method comprising:

determining that a first module is declared with a corresponding first module name;

determining that the first module is associated with a second module name;

responsive to determining that the first module is associated with the second module name;

synthesizing a second module declared with the second module name;

defining a first dependency of the second module, with the second module name, on the first module with the first module name,

wherein the first dependency of the second module is a transitive dependency based on a determination that the first module exposes an application programming interface (API), and

wherein the method is performed by at least one device comprising a hardware processor.

19. A system comprising:

one or more hardware processors; and

one or more one or more non-transitory computer-readable media storing instructions, which when executed by the one or more hardware processors, cause execution of operations comprising;

determining that a first module is declared with a corresponding first module name;

determining that the first module is associated with a second module name;

responsive to determining that the first module is associated with the second module name;

synthesizing a second module declared with the second module name;

defining a first dependency of the second module, with the second module name, on the first module with the first module name,

wherein the first dependency of the second module is a transitive dependency based on a determination that the first module exposes an application programming interface (API).