Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix license header check #905

Merged
merged 1 commit into from
Jul 22, 2020
Merged

Fix license header check #905

merged 1 commit into from
Jul 22, 2020

Conversation

glbrntt
Copy link
Collaborator

@glbrntt glbrntt commented Jul 22, 2020

Motivation:

The license header script silently stopped working when we let it find
all issues before exiting.

Modifications:

  • Fix script
  • Fix bad indentation in header

Result:

Licnese checking works again.

Motivation:

The license header script silently stopped working when we let it find
all issues before exiting.

Modifications:

- Fix script
- Fix bad indentation in header

Result:

Licnese checking works again.
@glbrntt glbrntt added the semver/none No version bump required. label Jul 22, 2020
@glbrntt glbrntt requested a review from Lukasa July 22, 2020 09:02
@glbrntt glbrntt merged commit a3ac0dd into grpc:master Jul 22, 2020
@glbrntt glbrntt deleted the gb-fix-script branch July 22, 2020 09:29
glbrntt added a commit to glbrntt/grpc-swift that referenced this pull request Aug 3, 2020
Motivation:

The "gRPC-Core" cocoapod specifies its module name as "grpc"; this is
unfortunate because we also specify our module name as "GRPC". This is
problematic of both are used in the same dependency graph. In CocoaPods
`module_name` is "name to use for the framework / clang module which
will be generated". We therefore end up with two "GRPC" frameworks.

If the module name is not specified it will default to the spec name
instead.

Modifications:

- Don't generate a custom module name when generating Podspecs
- Delete trailing whitespace

Result:

- Resolves grpc#905
- Generated frameworks match Podspec names (i.e. "gRPC-Swift" gets
  converted to "gRPC_Swift")
glbrntt added a commit that referenced this pull request Aug 3, 2020
Motivation:

The "gRPC-Core" cocoapod specifies its module name as "grpc"; this is
unfortunate because we also specify our module name as "GRPC". This is
problematic of both are used in the same dependency graph. In CocoaPods
`module_name` is "name to use for the framework / clang module which
will be generated". We therefore end up with two "GRPC" frameworks.

If the module name is not specified it will default to the spec name
instead.

Modifications:

- Don't generate a custom module name when generating Podspecs
- Delete trailing whitespace

Result:

- Resolves #905
- Generated frameworks match Podspec names (i.e. "gRPC-Swift" gets
  converted to "gRPC_Swift")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/none No version bump required.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants