[
https://issues.apache.org/jira/browse/BEAM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Kedigehalli updated BEAM-1632:
------------------------------------
Description: bigtable-protos include generated classes like
'com.google.rpc.Code' in its jar rather than depending on
'grpc-google-common-protos'. This conflicts with 'Datastore' dependencies. I am
not sure what the right solution is but for now the workaround is to tag the
usage of 'grpc-google-common-protos' as 'usedDependency' to prevent
'maven-dependency:analyze' issues. (was: bigtable-protos include generated
classes like 'com.google.rpc.Code' in its jar rather than depending on
'grpc-google-common-protos'. I am not sure what the right solution is but for
now the workaround is to tag the usage of 'grpc-google-common-protos' as
'usedDependency' to prevent 'maven-dependency:analyze' issues. )
> Current bigtable protos include google rpc generated classes in its jar
> -----------------------------------------------------------------------
>
> Key: BEAM-1632
> URL: https://issues.apache.org/jira/browse/BEAM-1632
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-gcp
> Reporter: Vikas Kedigehalli
> Assignee: Daniel Halperin
> Priority: Minor
>
> bigtable-protos include generated classes like 'com.google.rpc.Code' in its
> jar rather than depending on 'grpc-google-common-protos'. This conflicts with
> 'Datastore' dependencies. I am not sure what the right solution is but for
> now the workaround is to tag the usage of 'grpc-google-common-protos' as
> 'usedDependency' to prevent 'maven-dependency:analyze' issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)