[
https://issues.apache.org/jira/browse/BEAM-4087?focusedWorklogId=224993&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-224993
]
ASF GitHub Bot logged work on BEAM-4087:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Apr/19 13:34
Start Date: 09/Apr/19 13:34
Worklog Time Spent: 10m
Work Description: adude3141 commented on issue #8255: [DO NOT
MERGE][BEAM-4087] implement configurable dependency versions
URL: https://github.com/apache/beam/pull/8255#issuecomment-481253944
Rethinking: The suggestion above (i.e. looping) is probably not what we
really want to test.
We likely want to assemble with default version and only *run* tests with
those different version as this will probably closest to what is happening,
when user change provided dependency.
That seems currently difficult together with shadow configuration, as this
impacts compile also. Need to do some reading here. Of course a hackish
solution is always possible...
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 224993)
Time Spent: 1h 20m (was: 1h 10m)
> 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: Sub-task
> Components: build-system
> Affects Versions: 2.5.0
> Reporter: Ismaël Mejía
> Assignee: Michael Luckey
> Priority: Major
> Time Spent: 1h 20m
> 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
(v7.6.3#76005)
