The current approach is to check out and build the corresponding components when the MVD is deployed.
The goal of this feature is to define and implement a dependency management process, which leverages Maven artifacts at least for some of the dependencies. The dependency management process should allow to better manage dependencies once the basic components are in place.
The MVD should also use the published EDC artifacts, to demonstrate how ECD artefacts can be consumed.
Acceptance Criteria
[ ] Concept for dependency management is defined and documented
[ ] RegistryService and Identity Hub artefacts are published
[ ] MVD consumes artefacts from EDC, RegistryService and IdentityHub repositories
Description
The MVD has dependencies to several components that reside in individual repositories:
The current approach is to check out and build the corresponding components when the MVD is deployed.
The goal of this feature is to define and implement a dependency management process, which leverages Maven artifacts at least for some of the dependencies. The dependency management process should allow to better manage dependencies once the basic components are in place.
The MVD should also use the published EDC artifacts, to demonstrate how ECD artefacts can be consumed.
Acceptance Criteria
Stories