In this PR we introduce zAppBuild support of the MetadataStore and DBB 2.0. These changes are NOT compatible with any older versions of DBB. DBB 2.0 is required.
Noteworthy Changes:
Replacement of the RepositoryClient with the MetadataStore for collection and build result data storage.
All builds will use the new SearchPathDependencyResolver and SearchPathImpactFinder APIs
Introduction of a new build property metadataStoreType controls which "version" of the MetadataStore to use. Valid options are 'file' and 'db2'. Default is 'file' which has no external dependencies.
With File MetadataStore, all operations which in the past required a RepositoryClient connection are now supported right out of the box (i.e. impactBuild) with no db connection necessary. This is useful for POC development before moving into production with the Db2 MetadataStore.
Removal of RepositoryClient/MetadataStore variable from language scripts. With the introduction of the MDS, we can now utilize the MetadataStoreFactory class to create a static MDS instance and retrieve that instance whenever we want. Thus, there is no need to pass around the object anymore. It has been removed from any places in the code where it is not being utilized, including the language scripts.
Removal of RepositoryClient/MDS as a method parameter. Similar to the point above, the RepositoryClient was included as a parameter in several methods throughout the code base. With the introduction of the MDS, this is no longer required, so it has been removed as a parameter in any methods across the board and replaced with the MetadataStoreFactory getter method to retrieve the instance.
In this PR we introduce zAppBuild support of the MetadataStore and DBB 2.0. These changes are NOT compatible with any older versions of DBB. DBB 2.0 is required.
Noteworthy Changes:
metadataStoreTypecontrols which "version" of the MetadataStore to use. Valid options are 'file' and 'db2'. Default is 'file' which has no external dependencies.