[jira] [Commented] (AMBARI-18051) Services should be able to provide their own pre-req checks by supplying a jar file

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-18051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575750#comment-15575750 ] 

Hudson commented on AMBARI-18051:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #148 (See [https://builds.apache.org/job/Ambari-branch-2.5/148/])
AMBARI-18594 - AMBARI-18051 Breaks Stack Upgrade Checks (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cb9db0aef3d2ee6c11d9d7f15c4a4709c14dd1a8])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProviderTest.java


> Services should be able to provide their own pre-req checks by supplying a jar file
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-18051
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18051
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>             Fix For: trunk, 2.5.0, 2.4.2
>
>         Attachments: AMBARI-18051.patch
>
>
> Services should be able to provide their own pre-req checks by supplying a jar file.
> This would allow custom services to supply their own jar files to handle pre-req checks rather than forcing third party developers to make changes to ambari-server code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)