[
https://issues.apache.org/jira/browse/FLINK-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290779#comment-15290779
]
Stefano Bortoli commented on FLINK-1827:
----------------------------------------
Moving the classes from test to main does not allow to skip test because there
are dependencies with classes in test-jar of core and runtime. The tie with the
runtime test classes is rather extensive. Specially through the TestiUtils.
Also the flink-test component has all classes just in the test folder. Are you
sure you want to move the classes to the main folder for the test-utils? If you
want to make such component a utility for developers, it should become much
more substantial than what it is now. Perhaps it would be better even as an
external project.
> 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
> Fix For: 1.1.0
>
> 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)
