[
https://issues.apache.org/jira/browse/FLINK-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073863#comment-16073863
]
ASF GitHub Bot commented on FLINK-7074:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/4252#discussion_r125503520
--- Diff: flink-runtime/pom.xml ---
@@ -117,6 +117,16 @@ under the License.
</dependency>
<dependency>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-log4j12</artifactId>
--- End diff --
The problem I had was that I couldn't start the `TaskManagerRunner#main`
from within Intellij, because the class `org.apache.log4j.Level` could not be
found. If I'm not mistaken, then we filter out the log4j dependencies when
building the dist packages.
> Add entry point for TaskManagerRunner
> -------------------------------------
>
> Key: FLINK-7074
> URL: https://issues.apache.org/jira/browse/FLINK-7074
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Labels: flip-6
>
> Adding a {{main}} method to the {{TaskManagerRunner}} will allow us to use
> this class as the entry point for the code running inside a Mesos task or in
> a Yarn container. In this method, we have to setup the components of the
> {{TaskManager}}. It might be possible to share common setup logic between the
> TaskManager's entry point and the cluster entry point.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
