Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Schema
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 30
    • Issues 30
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe Software
  • Platform
  • System
  • Schema
  • Merge requests
  • !264

Upgrade First Party Library Dependencies for Release 0.14

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed David Diederich requested to merge dependency-upgrade into master Mar 29, 2022
  • Overview 1
  • Commits 3
  • Pipelines 4
  • Changes 5

This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release. The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability. However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated. Furthermore, the upgrade should only be merged in the CI pipeline reports success.

If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library. But significant upgrade efforts should not occur on this MR, as part of the release tagging process. Instead, significant work should be scheduled for a subsequent milestone.

Dependency Information Before the Upgrade

Branch: master
SHA:    36b05fad3414ee4a382a0a0000d04b42a1bf8947
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0-rc2 0.6.1
core-lib-gcp 0.14.0-rc2
os-core-lib-aws 0.13.0 0.3.16
obm 0.13.1-SNAPSHOT
oqm 0.13.0-SNAPSHOT
os-core-common 0.13.0 0.13.0
os-core-lib-ibm 0.13.0 0.7.0
osm 0.13.0-SNAPSHOT
(3rd Party) net.minidev.json-smart 2.4.7 2.3
(3rd Party) org.apache.logging.log4j.log4j-api 2.17.1 2.13.3
(3rd Party) org.apache.logging.log4j.log4j-core 2.17.1 2.13.3
(3rd Party) org.apache.logging.log4j.log4j-jul 2.17.1 2.13.3
(3rd Party) org.apache.logging.log4j.log4j-slf4j-impl 2.17.1 2.13.3

Dependency Information After the Upgrade

Branch: dependency-upgrade
SHA:    57f28fec301545aca644bed21b3a001862501233
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0 0.6.1
core-lib-gcp 0.14.0
os-core-lib-aws 0.14.0 0.3.16
obm 0.14.0
oqm 0.14.0
os-core-common 0.14.0 0.14.0
os-core-lib-ibm 0.14.0 0.7.0
osm 0.14.0
(3rd Party) net.minidev.json-smart 2.4.7 2.3
(3rd Party) org.apache.logging.log4j.log4j-api 2.17.1 2.13.3
(3rd Party) org.apache.logging.log4j.log4j-core 2.17.1 2.13.3
(3rd Party) org.apache.logging.log4j.log4j-jul 2.17.1 2.13.3
(3rd Party) org.apache.logging.log4j.log4j-slf4j-impl 2.17.1 2.13.3
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: dependency-upgrade