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?
Regards, Anton On Thu, May 17, 2018 at 4:04 PM Thomas Weise <[email protected]> wrote: > Hi, > > Is the following dependency intended or an oversight? > > > https://github.com/apache/beam/blob/06c70bdf871c5da8a115011b43f8072916cd79e8/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/pubsub/TestPubsub.java#L32 > > It appears that dependent code is in test scope. > > Should the build flag this (the maven build fails)? > > Thanks > >
