Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • W wks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • 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
  • Data Flow
  • Data EnrichmentData Enrichment
  • wks
  • Merge requests
  • !174

Upgrade First Party Library Dependencies for Release 0.15

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed David Diederich requested to merge dependency-upgrade into master Jun 07, 2022
  • Overview 1
  • Commits 4
  • Pipelines 3
  • Changes 6

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...
Preparing packages...
Branch: master
SHA:    34b34d673622546445d07f36887db2994466d81a
Maven:  0.15.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0 0.11.0
core-lib-gcp 0.14.0 0.1.17
os-automation-test-common-lib 0.11.0
obm 0.14.0
oqm 0.14.0
os-core-common 0.14.0 0.11.0
osm 0.14.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.11.4 2.11.4
(3rd Party) net.minidev.json-smart 2.4.7 2.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

Preparing packages...
Preparing packages...
Branch: dependency-upgrade
SHA:    029862fad4899302ed66b9411b8b101479c4b136
Maven:  0.15.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.15.0 0.11.0
core-lib-gcp 0.15.0 0.1.17
os-automation-test-common-lib 0.11.0
obm 0.15.0
oqm 0.15.0
os-core-common 0.15.0 0.11.0
osm 0.15.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.11.4 2.11.4
(3rd Party) net.minidev.json-smart 2.4.7 2.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
Reviewers
Request review from
Time tracking
Source branch: dependency-upgrade