## What changes were proposed in this pull request? With management packs and stacks being moved out of Ambari's source control, framework components such as upgrade checks and upgrade configuration actions will be to be delivered as part of the 3rd party stack and no long checked into Apache.
However, Ambari does not expose any kind of API/SPI/library for consumers to use when creating their own custom classes. A new maven-compatible project should be created as a home for classes which we expect our 3rd party consumers to use when creating custom plugins to be delivered in their stacks. They can then compile their code against this API/SPI and deliver a JAR which can be discovered and loaded by Ambari. - Some core classes, such as `AmbariException` must now live in this new package. We'll keep the packaging the same to prevent tons of changes to `ambari-server` module. - Only some reference classes are checked in for now (such as upgrade checks). Future commits will begin switching over `ambari-server` to use the new module. - A future commit will do the work to publish to Maven Central. ## How was this patch tested? Performed a build locally. [ Full content available at: https://github.com/apache/ambari/pull/2373 ] This message was relayed via gitbox.apache.org for [email protected]
