Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • I Indexer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • 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 SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Indexer
  • Merge requests
  • !301

Upgrade First Party Library Dependencies for Release 0.14

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed David Diederich requested to merge dependency-upgrade into master Mar 29, 2022
  • Overview 1
  • Commits 1
  • Pipelines 2
  • Changes 9

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

Preparing packages...
Branch: master
SHA:    cfdbcd6a9f0d1a7df0604d1d838cdbd88163c4fb
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0-rc2 0.12.0-rc10
core-lib-gcp 0.14.0-rc2, 0.10.0
os-core-lib-aws 0.13.0 0.3.16
obm 0.13.1-SNAPSHOT
oqm 0.13.0-SNAPSHOT
os-core-common 0.14.0-rc4 0.14.0-rc4
os-core-lib-ibm 0.13.0 0.13.0
osm 0.13.0-SNAPSHOT
(3rd Party) net.minidev.json-smart 2.4.7 2.4.6
(3rd Party) org.apache.logging.log4j.log4j-api 2.17.1 2.11.1, 2.11.2, 2.13.0
(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-to-slf4j 2.17.1 2.11.2, 2.13.0

Dependency Information After the Upgrade

Preparing packages...
Branch: dependency-upgrade
SHA:    f812a5cadee154e2e4b7e1d2bb4b4370bc441d14
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0 0.12.0-rc10
core-lib-gcp 0.14.0, 0.10.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.14.0
osm 0.14.0
(3rd Party) net.minidev.json-smart 2.4.7 2.4.6
(3rd Party) org.apache.logging.log4j.log4j-api 2.17.1 2.11.1, 2.11.2, 2.13.0
(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-to-slf4j 2.17.1 2.11.2, 2.13.0
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: dependency-upgrade