Skip to content

Conversation

@pgr0ss
Copy link
Contributor

@pgr0ss pgr0ss commented Aug 11, 2017

This commit aligns the naming of the Bazel Maven jars with the names
used by Bazel's migration-tooling project:

https://github.com/bazelbuild/migration-tooling

Unfortunately, we can't fix @com_google_protobuf_java because it's
required by Bazel itself.

Fixes #3328

This commit aligns the naming of the Bazel Maven jars with the names
used by Bazel's migration-tooling project:

https://github.com/bazelbuild/migration-tooling

Unfortunately, we can't fix @com_google_protobuf_java because it's
required by Bazel itself.

Fixes grpc#3328
@grpc-kokoro
Copy link

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Copy link
Member

@ejona86 ejona86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@ejona86
Copy link
Member

ejona86 commented Aug 11, 2017

Okay to test

@ejona86
Copy link
Member

ejona86 commented Aug 11, 2017

The naming convention is actually defined clearly in the documentation for maven_jar.

@ejona86 ejona86 merged commit 72b9ee2 into grpc:master Aug 11, 2017
@pgr0ss pgr0ss deleted the fix_bazel_maven_names branch August 15, 2017 17:18
@lock lock bot locked as resolved and limited conversation to collaborators Jan 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mismatch in naming with bazel maven jars

3 participants