You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/08/12 16:38:00 UTC
[jira] [Work logged] (BEAM-7954) Beam should only use guava imports
coming from vendored guava
[ https://issues.apache.org/jira/browse/BEAM-7954?focusedWorklogId=293250&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-293250 ]
ASF GitHub Bot logged work on BEAM-7954:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/19 16:37
Start Date: 12/Aug/19 16:37
Worklog Time Spent: 10m
Work Description: iemejia commented on pull request #9316: [BEAM-7954] Validate beam modules to disable guava imports from vendored gRPC
URL: https://github.com/apache/beam/pull/9316
R: @lukecwik
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 293250)
Time Spent: 10m
Remaining Estimate: 0h
> Beam should only use guava imports coming from vendored guava
> -------------------------------------------------------------
>
> Key: BEAM-7954
> URL: https://issues.apache.org/jira/browse/BEAM-7954
> Project: Beam
> Issue Type: Bug
> Components: build-system, sdk-java-core
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: Minor
> Fix For: 2.15.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> gRPC vendors guava too and some Beam classes have mistakenly started to use guava coming from the vendored gRPC dependency. We should probably restrict the use of Guava only to its vendored dependency.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)