-
Notifications
You must be signed in to change notification settings - Fork 3
Component collection
The functionality includes a module crce-component-collection
. Management and support is integrated in the crce-webui-v2
module of the graphical user interface web application. The functionality allows you to manage the life cycle of artefact sets. The existing Mongo DB database system is used to store collection records. The collection record is identified by a unique _id string in the database. Furthermore, the record contains the name, version, list of resources included (their id records in the Mongo database). Other record entries are a list of configuration parameters and version range defined artifacts.
Compiling a component is possible as part of building a CRCE application - see module list in crce-modules-reactor
.
Module functionality allows you to manage a set of artifacts as a whole. The module contains two documented interfaces: CollectionServiceApi
and ExportCollectionServiceApi
. The current lifecycle management functions are: create a new collection, edit, copy, delete. The function also allows you to export a set of artifacts, including their metadata in XML format, to archive ZIP. If the artifact report is defined by their names, the corresponding compatible version will supply the CRCE repository. Currently, this ability is not fully functional. This is a continuation of the CRCE functionality. The module function now provides the largest or smallest available version of the artifact in the Store, according to user settings.
Roman Pesek, 2019
[ CRCE wiki ]