You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2015/04/08 13:55:12 UTC

[jira] [Commented] (FLINK-1827) Move test classes in test folders and fix scope of test dependencies

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

Stephan Ewen commented on FLINK-1827:
-------------------------------------

I agree, that would be a good fix.

Is that problem only in {{flink-test-utils}}, or also in other projects?

> Move test classes in test folders and fix scope of test dependencies
> --------------------------------------------------------------------
>
>                 Key: FLINK-1827
>                 URL: https://issues.apache.org/jira/browse/FLINK-1827
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: 0.9
>            Reporter: Flavio Pompermaier
>            Priority: Minor
>              Labels: test-compile
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Right now it is not possible to avoid compilation of test classes (-Dmaven.test.skip=true) because some project (e.g. flink-test-utils) requires test classes in non-test sources (e.g. scalatest_${scala.binary.version})
> Test classes should be moved to src/main/test (if Java) and src/test/scala (if scala) and use scope=test for test dependencies



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