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

ASF GitHub Bot commented on FLINK-1379:
---------------------------------------

GitHub user lresende opened a pull request:

    https://github.com/apache/zeppelin/pull/1370

    [FLINK-1379] Flink interpreter is missing scala libraries

    ### What is this PR for?
    On Flink interpreter, remove provided scope from scala libraries to enable 
copying them to interpreter location.
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### What is the Jira issue?
    [ZEPPELIN-1379](https://issues.apache.org/jira/browse/ZEPPELIN-1379)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lresende/incubator-zeppelin flink-dependencies

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1370.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1370
    
----
commit 7d39c0d040a29ed92b515a70862bcd7a9e7c0824
Author: Luciano Resende <lrese...@apache.org>
Date:   2016-08-26T19:49:19Z

    [FLINK-1379] Flink interpreter is missing scala libraries
    
    Remove provided scope from scala libraries to enable copying
    them to interpreter location.

----


> add RSS feed for the blog
> -------------------------
>
>                 Key: FLINK-1379
>                 URL: https://issues.apache.org/jira/browse/FLINK-1379
>             Project: Flink
>          Issue Type: Improvement
>          Components: Project Website
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Minor
>         Attachments: feed.patch
>
>
> I couldn't find an RSS feed for the Flink blog. I think that a feed helps a 
> lot of people to stay up to date with the changes in Flink. 
> [FLINK-391] mentions a RSS feed but it does not seem to exist.



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

Reply via email to