Refactor for Reference Implementation
Type of change
-
Bug Fix -
Feature
https://gitlab.opengroup.org/osdu/pmc/community-implementation/-/issues/5
More details about the solution: https://community.opengroup.org/osdu/documentation/-/wikis/Pluggable-approach-for-Mappers-and-Drivers
As a part of the community implementation solution GC module was refactored to the Core-Plus module, in addition new pluggable approach for Drivers was used.
What is the current behavior?
- We do not have the core-plus module.
- Drivers not pluggable, all dependencies bounded during the compile step.
What is the new/expected behavior?
- We have the core-plus module.
- Drivers are pluggable and could be attached to service during image build, not compile.
Dev Checklist:
- Start
-
Copy ./provider/service-gc to ./service-core-plus
-
- Dependencies
-
Add core-plus
as a module to the root pom file, located in ./pom.xml -
Replace Google Drivers OQM, OBM, OSM with latest Community Core Drivers OQM, OBM, OSM, ex: old oqm new os-oqm-core -
Replace core-lib-gc with core-plus-common-lib -
Add spring boot loader dependency. -
Update spring-boot-maven
plugin, to use PropertiesLauncher as a main class. -
Remove Google Cloud dependencies, except Google Datastore (it's a known issue. Datastore dependency should accompany OSM, if you had to add it please update the issue with the project link).
-