[
https://issues.apache.org/jira/browse/BEAM-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732436#comment-16732436
]
Scott Wegner commented on BEAM-6056:
------------------------------------
{quote}I am not certain if it is user-visible whether or not we cherry-pick
Scott's most recent change.{quote}
The important change is [PR#7328|https://github.com/apache/beam/pull/7328]
which bumps the vendored gRPC artifact version to 0.2; this will ensure we
start consuming the latest published release with the fixes for JNI. This PR
should be cherry-picked into the release.
[PR#7388|https://github.com/apache/beam/pull/7388] is a change to the internal
build process, consuming the vendored gRPC artifact from Maven Central rather
than building it. I don't believe this makes a difference for release binaries;
the POM files we generate and publish for the release should reference the
correct gRPC artifact dependency either way. However, it seems safer to include
this just-in-case.
{quote}Will the release verification processes catch this if there is a
problem?{quote}
Building and running examples via the maven archetype project should verify
that the published artifacts are correct. However, I'm not sure if we have
release automation which will catch whether the previous JNI issue is fixed.
[~altay] do you know?
> Migrate gRPC to use vendoring library and vendoring format
> ----------------------------------------------------------
>
> Key: BEAM-6056
> URL: https://issues.apache.org/jira/browse/BEAM-6056
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Luke Cwik
> Assignee: Kenneth Knowles
> Priority: Minor
> Labels: portability
> Fix For: 2.10.0
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> This thread discusses the work:
> https://lists.apache.org/thread.html/4c12db35b40a6d56e170cd6fc8bb0ac4c43a99aa3cb7dbae54176815@%3Cdev.beam.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
