Updated git submodule commit references to latest master branch commits

[dmccoystephenson]

PR Details

Description

The git submodule commit references are currently pointing to commits that are 4 months old. These should be pointing to the latest commits on the master branch for each respective git submodule.

It should be noted that while this is technically a new version, the versions in the pom.xml files have not been updated as there were no changes to the functionality of the ODE.

Related Issue

No related issue.

Motivation and Context

It is important that these git submodule commit references are pointing to compatible versions of the git submodules. At this time, a user that clones the project and runs git submodule update will have git submodule versions that are incompatible with v2 of the ODE.

How Has This Been Tested?

Running git submodule update --init --recursive on a fresh clone of the 'jpo-ode' project results in the proper versions of the git submodules being targeted:

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)
• Git submodule commit reference updates

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
  ODE Contributing Guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[drewjj]

Looks like the new commit references check out.

[payneBrandon]

ltgm, referenced module commits are all the latest tagged versions of the respective submodules.

[dan-du-car]

Thank you for this update!