[
https://issues.apache.org/jira/browse/FLINK-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312296#comment-15312296
]
Maximilian Michels commented on FLINK-4009:
-------------------------------------------
Yes, this issue could be a sub task of FLINK-3454.
You added the flink-ml dependency in the pom which ensures the library is added
to the test's class path. Then, the classpath is searched by the test which
could be fixed in this issue.
> Scala Shell fails to find library for inclusion in test
> -------------------------------------------------------
>
> Key: FLINK-4009
> URL: https://issues.apache.org/jira/browse/FLINK-4009
> Project: Flink
> Issue Type: Test
> Components: Scala Shell, Tests
> Affects Versions: 1.1.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Labels: test-stability
> Fix For: 1.1.0
>
>
> The Scala Shell test fails to find the flink-ml library jar in the target
> folder. This is due to its working directory being expected in
> "flink-scala-shell/target" when it is in fact "flink-scala-shell". I'm a bit
> puzzled why that could have changed recently. The last incident I recall
> where we had to change paths was when we introduced shading of all artifacts
> to produce effective poms (via the force-shading module). I'm assuming the
> change of paths has to do with switching from Failsafe to Surefire in
> FLINK-3909.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
