You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/07/07 15:41:00 UTC
[jira] [Commented] (BEAM-2557) DirectRunner should not have a hard
dependency on Hamcrest
[ https://issues.apache.org/jira/browse/BEAM-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078256#comment-16078256 ]
Kenneth Knowles commented on BEAM-2557:
---------------------------------------
I'm going to take a stab at fixing this.
> DirectRunner should not have a hard dependency on Hamcrest
> ----------------------------------------------------------
>
> Key: BEAM-2557
> URL: https://issues.apache.org/jira/browse/BEAM-2557
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Blocker
> Fix For: 2.1.0
>
>
> It seems that https://github.com/apache/beam/pull/3161/files introduced a hard dependency from the DirectRunner to TestPipelineOptions. But those options are only really appropriate for test scope - they incur a hard dependency on Hamcrest. From what I can tell, you really just want to tweak the DirectRunner behavior so the one flag could go in DirectPipelineOptions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)