Managing split packages in a module system
AssigneeOracle International Corporation
InventorsAlexander R. Buckley, Lai Hung Mandy Chung, Mark B. Reinhold, Alan Bateman
Life of this patent
Estimating the term…
Abstract
Techniques for managing split packages in a module system are disclosed. A code conflict exists between two packages, in different modules, based at least in part on the packages being named identically and including executable code. No code conflict exists between two other identically-named packages, in different modules, based at least in part on the packages not including any executable code. Managing split packages may be based, at least in part, on module membership records associated with the modules.
Claims20
A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:
- identifying a first set of one or more packages in a first module;
- determining that a first package, from the first set of one or more packages, comprises a first set of executable code;
- generating a first module membership record for the first module, wherein based at least in part on the first package comprising the first set of executable code, the first module membership record indicates that the first package belongs to the first module;
- identifying a second set of one or more packages in a second module;
- determining that a second package, from the second set of one or more packages, does not comprise any sets of executable code;
- and
- generating a second module membership record for the second module, wherein based at least in part on the second package not comprising any sets of executable code, the second module membership record does not indicate that the second package belongs to the second module.
A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:
- identifying a first package in a first module;
- identifying a second package in a second module;
- determining that (a) the first package and the second package are named identically and (b) the first package and the second package each comprise corresponding executable code;
- determining, based at least in part (a) and (b), that a first code conflict exists between the first module and the second module;
- identifying a third package in a third module;
- identifying a fourth package in a fourth module;
- determining that (c) the third package and the fourth package are named identically and (d) at least one of the third package and the fourth package does not comprise any executable code;
- and
- determining, based at least in part on (c) and (d), that no code conflict exists between the third module and the fourth module.
Dependencies are inferred from the claim text.