[jira] [Updated] (FLINK-2156) Scala modules cannot create logging file

["Till Rohrmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-2156:
---------------------------------
    Description: 
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.

  was:
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.


> Scala modules cannot create logging file
> ----------------------------------------
>
>                 Key: FLINK-2156
>                 URL: https://issues.apache.org/jira/browse/FLINK-2156
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
>            Priority: Minor
>
> 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)