Upgrade osgi-core to 8.0.0

[durgajagadeesh]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

• Upgrade osgi-core to 8.0.0

Change Log

• SPECS-EXTENDED/osgi-core/osgi-core-build.xml
• SPECS-EXTENDED/osgi-core/osgi-core.signatures.json
• SPECS-EXTENDED/osgi-core/osgi-core.spec
• osgi.core-8.0.0.pom
• cgmanifest.json

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx
• 

[durgajagadeesh]

This package has been built successfully along with osgi-annotation.

-Thank you!

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1010169&view=results

[sandeepkarambelkar]

@durgajagadeesh There are license check failures. Can you check them?

##[warning]License issues found.
WARN: (osgi-core-javadoc-8.0.0-3.azl3.noarch.rpm) has license warnings:
bad %doc files:
/usr/share/javadoc/osgi-core/legal/ADDITIONAL_LICENSE_INFO
duplicated license files:
/usr/share/javadoc/osgi-core/legal/LICENSE

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1010278&view=results

[durgajagadeesh]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1010278&view=results

Hi @sandeepkarambelkar, buddy build has been completed. Successfully.
-Thank you!

[sandeepkarambelkar]

Buddy Build Successful.
Changes LGTM

[kgodara912]

As such package upgrade looks fine. Buddy build is successful. Please address minor nit.

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1011121&view=results

[durgajagadeesh]

Hi @sandeepkarambelkar, could you please retrigger buddy build once again with run time dependency only with osgi-annotation.

[sandeepkarambelkar]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1011878&view=results

[kgodara912]

Buddy build after latest commit.

[durgajagadeesh]

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1011878&view=results

Hi @sandeepkarambelkar, I’ve resolved the license warning.

INFO[0004][licensecheck] Search results for (/mnt/vss/_work/1/s/out/RPMS):
WARN: (osgi-compendium-javadoc-7.0.0-2.azl3.noarch.rpm) has license warnings:
bad %doc files:
/usr/share/javadoc/osgi-compendium/legal/ADDITIONAL_LICENSE_INFO
duplicated license files:
/usr/share/javadoc/osgi-compendium/legal/LICENSE

Could you please trigger the buddy build again? Thanks!

[kgodara912]

Buddy build is successful. Version upgrade in extended repo and fixes for license warnings in both specs. LGTM.