You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (JIRA)" <ji...@apache.org> on 2015/10/06 20:35:26 UTC
[jira] [Comment Edited] (FLINK-2156) Scala modules cannot create
logging file
[ https://issues.apache.org/jira/browse/FLINK-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945531#comment-14945531 ]
Dawid Wysakowicz edited comment on FLINK-2156 at 10/6/15 6:34 PM:
------------------------------------------------------------------
Hi,
This can be my first open-source contribution ever, hope I did everything right.
Beside suggested solution to set mvn.forkNumber to 1 I passed the variable log.dir to scalatest argLine because the commandLine parameters are not passed by default.
Looking forward to any comments.
was (Author: dawidwys):
Hi,
This can be my first open-source contribution ever, hope I did everything right.
Beside suggested solution to set mvn.forkNumber to 1 I passed the variable log.dir to scalatest argLine because the commandLine parameters are not passed by default.
> Scala modules cannot create logging file
> ----------------------------------------
>
> Key: FLINK-2156
> URL: https://issues.apache.org/jira/browse/FLINK-2156
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 0.10
> Reporter: Till Rohrmann
> Labels: starter
> Fix For: 0.10
>
>
> The Scala only modules {{flink-scala-shell}} and {{flink-ml}} use Maven's scalatest plugin to run their tests. The scalatest plugin has no {{forkNumber}}, though. Therefore, the logging fails to create the logging file as specified in the {{log4j-travis.properties}} file.
> We can fix this issue by giving these two modules different {{log4j.properties}} files which don't require a {{forkNumber}}. Or we fix the {{forkNumber}} to 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)