You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2018/01/12 19:27:05 UTC
[jira] [Updated] (SAMZA-1207) Samza should publish test utilities
in a test artifact
[ https://issues.apache.org/jira/browse/SAMZA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Maes updated SAMZA-1207:
-----------------------------
Fix Version/s: (was: 0.14.0)
0.15.0
> Samza should publish test utilities in a test artifact
> ------------------------------------------------------
>
> Key: SAMZA-1207
> URL: https://issues.apache.org/jira/browse/SAMZA-1207
> Project: Samza
> Issue Type: Bug
> Reporter: Jake Maes
> Assignee: Jake Maes
> Fix For: 0.15.0
>
>
> Samza has some handy tools in samza-test that are not published in a maven artifact.
> For example:
> 1. https://github.com/apache/samza/blob/2a3a5ac7f21dc4213ff6ec96e11a798bff096d04/samza-test/src/test/java/org/apache/samza/test/StandaloneIntegrationTestHarness.java
> 2. https://github.com/apache/samza/blob/2a3a5ac7f21dc4213ff6ec96e11a798bff096d04/samza-test/src/test/scala/org/apache/samza/test/integration/StreamTaskTestUtil.scala
> However, these utilities are in the src/test/* directory of samza-test and are therefore not published to an artifact.
> This ticket is to fix that. Two options come to mind:
> 1. Move all useful test utilities to the /src/main/* directory so they get published
> 2. Configure gradle/maven to publish a separate artifact for these.
> I think #1 would be cleaner.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)