-**Dynamic Dependency Wiring**: This solution enables dynamic dependency wiring at runtime, allowing for the swapping of dependencies as needed. The OSDU service relies on the Driver's self-sufficiency, which involves autonomous component assembly within the Driver. This approach fosters a loose coupling that allows for dependency swaps without requiring changes in the service. <br/>
-**Dynamic Dependency Wiring**: This solution enables dynamic dependency wiring at runtime, allowing for the swapping of dependencies as needed. The OSDU service relies on the Driver's self-sufficiency, which involves autonomous component assembly within the Driver. This approach fosters a loose coupling that allows for dependency swaps without requiring changes in the service. <br/>
-**Plugin usage is not mandatory**. Provider implementations could use community Drivers and their own Drivers as direct dependencies of their service implementation. The compile step configured for community Drivers is not mandatory for provider Drivers. Furthermore, the community Drivers will have 2 artifacts, the original jar which could be used as a regular dependency, and the Uber jar or plugin jar. <br/>
-**Plugin usage is not mandatory**. Provider implementations could use community Drivers and their own Drivers as direct dependencies of their service implementation. The compile step configured for community Drivers is not mandatory for provider Drivers. Furthermore, the community Drivers will have 2 artifacts, the original jar which could be used as a regular dependency, and the Uber jar or plugin jar. <br/>
- The plugin-based approach does not impose mandatory usage of Maven Shade and Uber jars.
- The plugin-based approach does not impose mandatory usage of Maven Shade and Uber jars.
- Providers have the option to introduce their drivers as they are and use them in the provider module as direct dependencies.
- Providers have the option to introduce their drivers as they are and use them in the provider module as direct dependencies.
- Additionally, the community's south decision point or core-plus module won't require providers to remove already bundled community dependencies since they are not present.
- Additionally, the community's south decision point or core-plus module won't require providers to remove already bundled community dependencies since they are not present.
