Centralize artifacts 27/89127/1
authorRobert Varga <robert.varga@pantheon.tech>
Sat, 18 Apr 2020 20:47:32 +0000 (22:47 +0200)
committerRobert Varga <robert.varga@pantheon.tech>
Sat, 18 Apr 2020 21:00:25 +0000 (23:00 +0200)
commit7027c7181a90ce183894c3cd17cd84a0bf4517b5
treeeece0ba5efebfc44b8798223155afeff767a51cf
parentae6388e37fab2bd6969bf0a0b72e5f3913a17584
Centralize artifacts

Rather than having three different sets of artifacts:
- mdsal-artifacts
- config-artifacts
- benchmark-artifacts

Create a project-wide controller-artifacts, just as the guidelines
tell us to. This has the benefit for downstreams, as they do not
need to track multiple versions. It also benefits us, as we have
a single place for tracking what we produce.

Change-Id: I73cc02c6f1df6c4d705ef83dfc57e6aad17c6287
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
24 files changed:
artifacts/pom.xml [moved from opendaylight/md-sal/mdsal-artifacts/pom.xml with 84% similarity]
benchmark/artifacts/pom.xml [deleted file]
benchmark/dsbenchmark/pom.xml
benchmark/ntfbenchmark/pom.xml
benchmark/pom.xml
benchmark/rpcbenchmark/pom.xml
docs/pom.xml
features/config-netty/odl-config-netty/pom.xml
features/mdsal/odl-controller-mdsal-common/pom.xml
features/mdsal/odl-controller-model-topology/pom.xml
features/mdsal/odl-mdsal-broker-local/pom.xml
features/mdsal/odl-mdsal-broker/pom.xml
features/mdsal/odl-mdsal-distributed-datastore/pom.xml
features/mdsal/odl-mdsal-model-inventory/pom.xml
features/mdsal/odl-mdsal-remoterpc-connector/pom.xml
features/mdsal/odl-message-bus-collector/pom.xml
opendaylight/blueprint/pom.xml
opendaylight/config/config-artifacts/pom.xml [deleted file]
opendaylight/config/pom.xml
opendaylight/md-sal/mdsal-it-base/pom.xml
opendaylight/md-sal/mdsal-it-parent/pom.xml
opendaylight/md-sal/parent/pom.xml
opendaylight/md-sal/pom.xml
pom.xml