Cartridge/Platform extensions dependency management

[RobertNorthard]

As a user/developer I want to know when my platform extension/cartridge/platman version depends on a specific version of ADOP core as this may prevent the platform extension from being loaded correctly.

An example of this issue is that PR #22 adding docker based platform support - the platform extension and platman require a specific version of nginx.

I imagine a platform extension depending on a specific version of platman and the core depending on a specific version of platman (or vice versa).

Platman dependency version could be defined in the platform extensions/cartridges metadata (version x.y.z or git commit ref etc). The current platform version could be stored in Jenkins as a global environment variable. The load cartridge/platform extensions Jenkins jobs would then first check if the current version of platman and ADOP core are supported by the platform extension. If not, inform the user that they need to perform a platform upgrade. This will enable Jenkins job to fail fast if versions are not compatible.

@nickdgriffin What are your opinions on this?

[RobertNorthard]

Closing as we have not had a use case for this.