You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/13 12:19:20 UTC

[jira] [Commented] (EAGLE-536) Suppport application dependency in framework

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

ASF GitHub Bot commented on EAGLE-536:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-eagle/pull/435


> Suppport application dependency in framework
> --------------------------------------------
>
>                 Key: EAGLE-536
>                 URL: https://issues.apache.org/jira/browse/EAGLE-536
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: v0.5.0
>            Reporter: Hao Chen
>            Assignee: Hao Chen
>             Fix For: v0.5.0
>
>
> In most cases a complete application maybe logically consist of a series of sub-applications, typically like 
> {code} JPM APP (logically) = JPM UI App + Spark History APP + Spark Running APP + MR History APP + MR Running APP {code}
> , where JPM UI APP should depends on other APP.
> So the enhancement should include:
> 1. Some APP may only have Process (appClass) and others may only have UI (viewPath)
> 2. Declare JPM UI APP's dependency
> 3. Check JPM UI APP dependency when installation, if not meet, throw exception.



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