THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Should ServiceDeploymentContributors be able to specify version ranges?
- How can a contributor that will likely work for every future version of a service declare that fact?
- How can a more contributor supporting a more specific version take precedence over a more generic?
- What happens during rolling upgrade where for example NameNodes of different versions are running?
- Should versions be specified as they are in Maven?