You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2020/04/28 21:20:00 UTC
[jira] [Reopened] (BEAM-4087) Gradle build does not allow to
overwrite versions of provided dependencies
[ https://issues.apache.org/jira/browse/BEAM-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía reopened BEAM-4087:
--------------------------------
This is still an issue even if the PR / approach was not merged. We still do not have a practical way to test multiple provided versions of a dependency, and this is probably the only issue bugging me still after 2 years of the move to gradle, we still work by faith based validation for things like multi version compatibility of Kafka and Spark.
It is a pity because this is so simple to do in maven that still surprises me that it demands so much effort to get it done in gradle.
I still think it is worth to explore a way to tackle this, or is there some new simpler way to do it now that I missed?
> Gradle build does not allow to overwrite versions of provided dependencies
> --------------------------------------------------------------------------
>
> Key: BEAM-4087
> URL: https://issues.apache.org/jira/browse/BEAM-4087
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Affects Versions: 2.5.0
> Reporter: Ismaël Mejía
> Priority: Major
> Labels: gradle
> Fix For: Not applicable
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> In order to test modules with provided dependencies in maven we can execute for example for Kafka `mvn verify -Prelease -Dkafka.clients.version=0.9.0.1 -pl 'sdks/java/io/kafka'` However we don't have an equivalent way to do this with gradle because the version of the dependencies are defined locally and not in the gradle.properties.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)