...
- No cross-project SNAPSHOT dependencies
- Teams to version and release their own artifacts on their own schedule
- Source control central an official ONAP artifact version manifest
- Teams to declare the “correct version” for cross-project use
- Manifests located in integration repo: https://git.onap.org/integration/tree/versions/
- Teams to declare the “correct version” for cross-project use
- TSC to approve version manifest for simultaneous release, e.g. Amsterdam
- Maven plugin to warn check against outdated dependencies vs. the manifest
- Teams to version bump their dependencies per their convenience
Benefits
- No unexpected build failures due to upstream SNAPSHOT changes
- No need for cross-project consolidated “mega builds” to check dependency issues
- Avoids issues with trying to synchronize artifact version numbers across projects
- Improved dev and build cycle time
...