My fault, I'll fix the maven issue.
I added this file and it is not in test intentionally. The purpose of this
class is similar to TestPipeline, in that other packages which depend on
GCP IO can use this class in tests, including integration tests. For
example, right now Beam SQL project depends on GCP IO project and uses both
TestPipeline and TestPubsub in the integration tests. Is there a better
approach for such use case?
On Thu, May 17, 2018 at 4:04 PM Thomas Weise <t...@apache.org> wrote:
> Is the following dependency intended or an oversight?
> It appears that dependent code is in test scope.
> Should the build flag this (the maven build fails)?