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

Fixes to protoc inputs to GenerateProtoTask #560

Merged

Conversation

clayburn
Copy link
Contributor

Addresses #457 and #557

This change will remove the OS from the input properties of the
GenerateProtoTask when `protoc` or a plugin is defined as a resolvable
artifact. The expectation is that same versions of `protoc` or plugins
will produce same outputs regardless of the OS on which they are run.

This is done by creating marking `alternativePaths` as Internal for
backwards compatibility and creating two new properties:
`releaseArtifacts` and `snapshotArtifacts`. `releaseArtifacts` will
contain "$groupId:$artifact:$version" for each non-snapshot dependency,
effectively ignoring OS for these dependencies. `snapshotArtifacts` will
contain each snapshot artifact in a `FileCollection` since the
snapshots cannot be matched solely by their maven coordinates.

See google#457.
This test should cover google#528 and show that it is no longer an issue.
@ejona86
Copy link
Collaborator

ejona86 commented Jun 6, 2022

@clayburn, thank you!

@clayburn clayburn deleted the 457-ignore-os-input-to-generateProtoTask branch June 6, 2022 21:10
@clayburn
Copy link
Contributor Author

@ejona86 - I've gotten a few pings about this PR. Are there any plans to make a release including this?

@ejona86
Copy link
Collaborator

ejona86 commented Jun 29, 2022

The release is done. Unfortunately, the coordinates changed, which may cause problems for some people. Apparently just adding maven-publish plugin to the build changes the behavior of the plugin-publish plugin (gradle/plugin-portal-requests#124). So I think I'll do another release. Release 0.8.19 is safe to use, but just annoying.

@ejona86
Copy link
Collaborator

ejona86 commented Jun 29, 2022

Actually... I guess I won't, and will just leave it as-is. Looking at the plugin-publish 1.0.0 release notes seems this is "the new way of doing things."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants