Resolve "Correct Internal Versioning" and "Upgrade Core Azure Dependency"
Closes #58 (closed), #59 (closed)
See osdu/platform&9 (closed) for more details.
MR's Raison d'être
This MR simultaneously solves the internal versioning of the build, and upgrades the core Azure lib to use the latest release candidate version of the library. Correcting the internal versioning is an essential first step to all library cleanups -- without it, the testing libraries are permanently locked to the decisions of a very old version of the core libraries. Azure had to be updated at the same time, because it referenced a non-existent version of the library. That would prevent any pipeline from finishing successfully.
Dependency Table, after the application of this MR's changes
| Maven Dependencies | Root POM | testing/ |
|---|---|---|
| os-core-common | 0.9.0, 0.10.0-SNAPSHOT | 0.9.0 |
| core.aws.os-core-lib-aws | 0.9.0 | 0.3.16 |
| core-lib-gcp | 0.9.0 | |
| os-core-lib-ibm | 0.7.0 | 0.7.0 |
| core-lib-azure | 0.10.0-rc10 | 0.10.0-rc10 |
Housekeeping Updates
FOSSA Update
This MR also updates the FOSSA attributions, since these need to be kept up to date on every MR. Changes are expected whenever the library dependencies are updated.
Update Deprecated Pipeline Includes
This MR also updates the .gitlab-ci.yml file to use the newer pipeline includes, rather than relying on deprecated includes that mimic old behavior. These housekeeping updates should be done regularly on MRs when they are discovered so the old CI include files can be deleted and no longer supported.
Testing POM Structure
This MR marks the child modules under testing/ as child modules. That allows proper detection of the root POMs for this project.