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/18 19:52:00 UTC
[jira] [Assigned] (BEAM-2237) SDK should have runtime hamcrest
dependency or should bundle it
[ https://issues.apache.org/jira/browse/BEAM-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles reassigned BEAM-2237:
-------------------------------------
Assignee: Thomas Groh
> SDK should have runtime hamcrest dependency or should bundle it
> ---------------------------------------------------------------
>
> Key: BEAM-2237
> URL: https://issues.apache.org/jira/browse/BEAM-2237
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Thomas Groh
>
> {{TestOptions}}, {{SerializableMatchers}}, and {{PAssert}} have compile-time dependencies on hamcrest. We scope it {{provided}} to avoid having it on the classpath at runtime.
> This has lots of pain points, but one that recently bit the Spark runner is that when {{TestOptions}} or any subinterface is registered, we gain a runtime dependency on Hamcest. So users of the Spark runner all had to provide it, even outside of testing.
> We should just simplify this to either not have this dependency (perhaps via some hacking to make shading possibly) or declare the dependency.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)