Introduction

The SDAP project comprises several subprojects which has, over time, resulted in different codebases written in different languages using different packaging requirements and hence being consumed by different tools/clients.

This wiki page is an effort to describe, in it's entirety, which SDAP release artifacts exist for release distribution. This will help us to better define the release management procedure as we begin to push more frequent releases and grow the SDAP community.

Subprojects

The following table lists SDAP subprojects, the continuous integration builds, SNAPSHOT artifacts (if any exist), generated release artifacts and the packaging environment one would use to consume the artifacts.

Subproject NameCI BuildSNAPSHOT RepositoryRelease ArtifactsPackaging Environment (how to consume artifacts)

incubator-sdap-nexus

  I don't think this will be getting released. Goal is to break this down further into subproject and release those projects individually. [SDAP-23] 

incubator-sdap-mudrod

https://builds.apache.org/view/S-Z/view/SDAP/job/sdap-mudrod/https://repository.apache.org/content/repositories/snapshots
  • JAR's for each module
  • binary release (.tar.gz, .zip)
  • source release (.tar.gz, .zip)
Maven, Gradle, etc.... any build system that can consume JAR artifacts.

incubator-sdap-doms

TBDTBD
  • Python wheel
  • binary release (.tar.gz, .zip)
  • source release (.tar.gz, .zip)
Bash

incubator-sdap-ningesterpy  

TBDTBD
  • Python wheel
  • binary release (.tar.gz, .zip)
  • source release (.tar.gz, .zip)
Bash

incubator-sdap-ningester  

TBDTBD
  • Single Runnable JAR
  • binary release (.tar.gz, .zip)
  • source release (.tar.gz, .zip)
  • Docker Image
Bash

incubator-sdap-edge

    

incubator-sdap-nexusproto  

TBDTBD
  • Single Library JAR
  • Python wheel
  • source release (.tar.gz, .zip) (Python and Java)
Pip
  • No labels