[
https://issues.apache.org/jira/browse/AMBARI-18050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526632#comment-15526632
]
Hudson commented on AMBARI-18050:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #85 (See
[https://builds.apache.org/job/Ambari-branch-2.5/85/])
AMBARI-18050 - Upgrade pre-req check code needs to be decoupled from (tthorpe:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=645f87e2f9337175ec1bb2d053c17193d3e39185])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java
> Upgrade pre-req check code needs to be decoupled from CheckDescription class
> ----------------------------------------------------------------------------
>
> Key: AMBARI-18050
> URL: https://issues.apache.org/jira/browse/AMBARI-18050
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Tim Thorpe
> Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-18050.patch
>
>
> Currently each pre-req check must add an entry in the CheckDescription enum.
> This limits the ability for third party stacks and extensions to provide
> their own pre-req checks.
> The CheckDescription enum should be rewritten as a class and each pre-req
> check class should create an instance of it. This will allow stacks and
> extensions to include their own pre-req checks in separate jar files without
> requiring changes to ambari-server java code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
