Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

The following table describes the current CCSDK repository contents, and which ONAP projects use their artifacts:

RepositoryContentsUsed byMaven groupIdCurrent Version


CasablancaDublinEl Alto 
StableSnapshotSnapshot
ccsdk/appsStandalone applications / microservicesSDNCorg.onap.ccsdk.apps0.3.30.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/cdsController Design Studio (self-service tool)SDNC, SOorg.onap.ccsdk.cdsN/A0.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/dashboardDashboard for OOMOOMorg.onap.ccsdk.dashboardN/A1.1.01.1.1-SNAPSHOT1.2.0-SNAPSHOT
ccsdk/distributionDocker images and directed graphsAPPC, SDNCorg.onap.ccsdk.distribution0.3.40.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/featuresKaraf features not specifically intended to be called by directed graphsSDNCorg.onap.ccsdk.features0.3.30.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/parentParent POM files, based on ONAP oparentAPPC, SDNCorg.onap.ccsdk.parent1.1.41.2.4N/A1.3.0-SNAPSHOT
ccsdk/platform/blueprintsBlueprintsDCAE, OOMorg.onap.ccsdk.platform.blueprints



ccsdk/platform/pluginsPluginsDCAE, OOMorg.onap.ccsdk.platform.plugins



ccsdk/sli/adaptorsResource adaptors, to be called from resource nodes in a directed graphAPPC, SDNCorg.onap.ccsdk.sli.adaptors0.3.30.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/sli/coreCore engine used to execute directed graphsAPPC, SDNCorg.onap.ccsdk.sli.core0.3.30.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/sli/northboundNorthbound interfacesAPPC, SDNCorg.onap.ccsdk.sli.northbound0.3.30.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/sli/pluginsJava plugins to be called from execute nodes in a directed graphAPPC, SDNCorg.onap.ccsdk.sli.plugins0.3.30.4.30.4.4-SNAPSHOT0.5.0-SNAPSHOT
ccsdk/storage/esaasElastic Storage as a ServiceDCAE, OOMorg.onap.ccsdk.storage.esaas



ccsdk/utilsUtilitiesDCAE, OOMorg.onap.ccsdk.utils1.1.11.2.01.2.1-SNAPSHOT1.3.0-SNAPSHOT


Several of these repositories are interrelated, and care must be taken to ensure that dependencies between repositories are managed so that circular dependencies are avoided.  The following diagram illustrates the dependency hierarchy for the inter-related CCSDK repositories:

These dependencies are transitive.  In other words:

  • ccsdk/parent has no dependencies
  • ccsdk/sli/core depends only on ccsdk/parent
  • ccsdk/cds depends on ccsdk/sli/core and ccsdk/parent
  • ccsdk/sli/adaptors, ccsdk/sli/northbound, ccsdk/sli/plugins and ccsdk/features are independent of each other but all depend on ccsdk/cds, ccsdk/sli/core, and ccsdk/parent
  • ccsdk/distribution depends on all the repositories above it
  • ccsdk/apps depends on ccsdk/distribution (for directed graphs) and on all the repositories above it


  • No labels