protobuf-go/cmd/protoc-gen-go/testdata/go.mod

module github.com/golang/protobuf/v2/cmd/protoc-gen-go/testdata

require (
	github.com/golang/protobuf v1.2.1-0.20190311234659-51c19b98ee31
	github.com/golang/protobuf/v2 v2.0.0
)

replace github.com/golang/protobuf/v2 => ../../..
internal/cmd/generate-protos: generate test for testdata Running "go build ./..." does not descend into testdata directories. However, the testdata in this repository is source code that is intended to build properly. We could rename the directory, but that does not test whether the generated packages can initialize properly. Thus, we generate a trivial test that simply blank imports all packages. Doing this reveals that some of the generated files have incorrect imports, leading to registration conflicts. To avoid introducing a dependency on gRPC from our go.mod file, we put the testdata directories in their own module. Also, we avoid running internal/testprotos through the grpc plugin because the servie and method definitions in that directory are more for testing proto file initialization rather than testing grpc generation. Change-Id: Iaa6a06449787a085200e31bc7606e3ac904d3180 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/164917 Reviewed-by: Damien Neil <dneil@google.com> 2019-03-01 18:11:42 -08:00			`module github.com/golang/protobuf/v2/cmd/protoc-gen-go/testdata`

			`require (`
all: fix travis after v1 update Change-Id: I3194f4d2e57903d7ae0d6c20bae551dc6ab7d8ce Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/166891 Reviewed-by: Joe Tsai <thebrokentoaster@gmail.com> 2019-03-11 17:00:48 -07:00			`github.com/golang/protobuf v1.2.1-0.20190311234659-51c19b98ee31`
internal/cmd/generate-protos: generate test for testdata Running "go build ./..." does not descend into testdata directories. However, the testdata in this repository is source code that is intended to build properly. We could rename the directory, but that does not test whether the generated packages can initialize properly. Thus, we generate a trivial test that simply blank imports all packages. Doing this reveals that some of the generated files have incorrect imports, leading to registration conflicts. To avoid introducing a dependency on gRPC from our go.mod file, we put the testdata directories in their own module. Also, we avoid running internal/testprotos through the grpc plugin because the servie and method definitions in that directory are more for testing proto file initialization rather than testing grpc generation. Change-Id: Iaa6a06449787a085200e31bc7606e3ac904d3180 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/164917 Reviewed-by: Damien Neil <dneil@google.com> 2019-03-01 18:11:42 -08:00			`github.com/golang/protobuf/v2 v2.0.0`
			`)`

			`replace github.com/golang/protobuf/v2 => ../../..`