You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/05/18 19:50:04 UTC
[jira] [Commented] (BEAM-2272) Test scope & runtime dependencies
need reevaluation
[ https://issues.apache.org/jira/browse/BEAM-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016350#comment-16016350 ]
Daniel Halperin commented on BEAM-2272:
---------------------------------------
This issue slipped from 2.0.0, but does need work for next stable release. Our dependency analysis needs to get better
> Test scope & runtime dependencies need reevaluation
> ---------------------------------------------------
>
> Key: BEAM-2272
> URL: https://issues.apache.org/jira/browse/BEAM-2272
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, runner-direct, sdk-java-core
> Reporter: Daniel Halperin
> Fix For: 2.1.0
>
>
> Now that SDK core has been thinned out, many of the modules that have it in their {{dependenciesToScan}} will need to update their test-scoped dependencies for things that moved out of SDK.
> Known examples include protobuf and XML and perhaps others.
> We should re-enable dependency analysis on test scope and manually validate and ignore specific known runtime/test-runtime dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)