[
https://issues.apache.org/jira/browse/BEAM-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788288#comment-16788288
]
Chamikara Jayalath commented on BEAM-6118:
------------------------------------------
Beam version 2.7.0 and later uses gRPC 1.13.1 but not sure if that will resolve
the conflict here.
I'm bit confused by following comment.
"If I add {{io.grpc:grpc-core:jar:1.6.1}} as an explicit dependency to my POM
file, it doesn't 'pin' the dependency as it still gets pulled in as a
sub-dependency by
{{com.google.cloud.dataflow:google-cloud-dataflow-java-sdk-all:jar:2.5.0}}."
[https://stackoverflow.com/questions/53424272/maven-conflict-in-java-app-with-google-cloud-core-grpc-dependency/53558702#53558702]
Shouldn't explicitly defining the dependency in pom.xml override it for all
transitive dependencies ?
> Maven dependency conflicts between google-cloud-pubsub and Apache Beam
> packages
> -------------------------------------------------------------------------------
>
> Key: BEAM-6118
> URL: https://issues.apache.org/jira/browse/BEAM-6118
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.5.0
> Reporter: Chris
> Priority: Major
> Labels: maven, triaged
>
> (I'm using BDD terminology to phrase the issue)
>
> AS A DEVELOPER I want to be able to use the following Maven dependencies (or
> newer versions) in the same Java project inside Eclipse SO THAT I can
> subscribe to a Google pub/sub independently from the mechanism supplied by
> Apache Beam, and efficiently update a dataset linked to my Apache Beam
> dataflow.
> I want to update my linked dataset by accepting push data that reflects
> changes to its data, instead of having to poll for new data each time I
> process an item from an Apache Beam pipeline that subscribes to a different
> Google pub/sub dataset.
>
> {code:java}
> <dependency>
> <groupId>com.google.cloud.dataflow</groupId>
> <artifactId>google-cloud-dataflow-java-sdk-all</artifactId>
> <version>2.5.0</version>
> </dependency>
> <dependency>
> <groupId>com.google.cloud</groupId>
> <artifactId>google-cloud-pubsub</artifactId>
> <version>1.53.0</version>
> </dependency>
> {code}
>
> ACCEPTANCE CRITERIA
> No dependency conflict related to io.grpc:grpc-core:jar is caused when I run
> {code:java}
> mvn clean install{code}
> against the project.
> Please see here (I documented itas a GitHub issue against the
> google-cloud-pubsub library, however it's primarily a Beam Maven dependency
> issue):
>
> [https://github.com/googleapis/google-cloud-java/issues/4095]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
