[jira] [Commented] (REEF-269) Refactor Launcher and LaunchClass

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

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

Andrew Chung commented on REEF-269:
-----------------------------------

I have a basic implementation for this but I don't think it's ready for CR yet, as it hasn't really been tested yet. Are there any existing code that tests the Launcher or the LaunchClass and the runtime configuration serializations? I was not able to find any.

> Refactor Launcher and LaunchClass
> ---------------------------------
>
>                 Key: REEF-269
>                 URL: https://issues.apache.org/jira/browse/REEF-269
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF
>    Affects Versions: 0.10
>            Reporter: Markus Weimer
>            Assignee: Andrew Chung
>
> The {{Launcher}}/{{LaunchClass}} combo is showing quite a bit of evolutionary baggage. For instance, [REEF-246] and [REEF-247] will have to deal with the weirdness of potentially instantiating two {{RemoteManager}} instances.
> Much of this oddness has its root in the split between command line options and configuration. The former is parsed in {{Launcher}}, the latter in {{LaunchClass}}. 
> One step to clean this up would be to have a new Launcher which only takes one command line parameter which points to a Configuration file. That is then loaded and immediately used to instantiate the {{Clock}}.



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