Overview

The ONAP Integration team is providing a Maven plugin to help individual projects detect when their external (cross-project) dependencies have become out of date.

The version manifest CSV itself is compiled into the the plugin, so that we can identify the exact manifest version using the plugin version number.

Running the Plugin

To use the latest available Version Manifest plugin, run the following command:

mvn org.onap.integration:version-manifest:version-check

To use a specific version (e.g. 0.1.0) of the Version Manifest plugin, run the following:

mvn org.onap.integration:version-manifest:0.1.0:version-check

These assume that you have the ONAP nexus repos defined in your ~/m2/settings.xml so that Maven can download the plugin artifacts.

Interpreting the Output

Here is a sample output provided by the plugin:

[INFO] --- version-manifest:0.1.0:version-check (default-cli) @ clds ---
[INFO] Checking version manifest /java-manifest.csv
[INFO] 
[WARNING] The following dependencies should be updated to match the version manifest:
[WARNING]   org.onap.oparent:oparent                                  1.0.0-SNAPSHOT -> 0.1.0
[INFO] 
[WARNING] The following dependencies are missing in the version manifest:
[WARNING]   org.onap.policy.common:ONAP-Logging                                1.1.0 ->     ?
[WARNING]   org.onap.policy.engine:ControlloopPolicy                  1.1.0-SNAPSHOT ->     ?
[WARNING]   org.onap.policy.engine:PolicyEngineAPI                             1.1.0 ->     ?
[INFO] 

Action Items

For warnings in the first section "should be updated to match the version manifest", please change your dependency to the version declared in the manifest.

For warnings in the second section "are missing in the version manifest", please contact the upstream team to get them to release their artifacts per Independent Versioning and Release Process and update the version manifest with the updated version numbers.