[
https://issues.apache.org/jira/browse/FLINK-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573280#comment-14573280
]
ASF GitHub Bot commented on FLINK-2080:
---------------------------------------
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/787
[FLINK-2080] Document how to use Flink with sbt
I've turned the patch from FLINK-2080 into a pull request ;)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rmetzger/flink flink2080
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/787.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 #787
----
commit e909c18618936eacd20f51466863216279130288
Author: Christian Wuerz <[email protected]>
Date: 2015-06-04T18:05:46Z
[FLINK-2080] Document how to use Flink with sbt
----
> Execute Flink with sbt
> ----------------------
>
> Key: FLINK-2080
> URL: https://issues.apache.org/jira/browse/FLINK-2080
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 0.8.1
> Reporter: Christian Wuertz
> Assignee: Christian Wuertz
> Priority: Minor
> Attachments: sbt.patch
>
>
> I tried to execute some of the flink example applications on my local machine
> using sbt. To get this running without class loading issues it was important
> to make sure that Flink is executed in its own JVM and not in the sbt JVM.
> This can be done very easily, but it would have been nice to know that in
> advance. So maybe you guys want to add this to the Flink documentation.
> An example can be found here: https://github.com/Teots/flink-sbt
> (The trick was to add "fork in run := true" to the build.sbt)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
