apache / apache/beam

Do not force our fixed dependency versions on all configurations, but only those we know about

Open
#18,881 0 comments 0 reactions 0 assignees View on GitHub
build gradle improvement P3
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

One example is the errorprone plugin has its own configuration which has nothing to do with our code. To use a different version of guava we do:

```

apply plugin: 'net.ltgt.errorprone'
dependencies {
errorprone 'com.google.guava:guava:22.0'

errorprone 'com.google.errorprone:error_prone_core:2.2.0'
}

```

But our build_rules.gradle has a bug that makes this not work, because we do:

```

configurations.all {
resolutionStrategy {
force library.java.values()
}
}

```

Instead of this "big hammer" approach, we should figure out a correct way to configure things. Possibly this should just be a list of a few Java configurations.

Imported from Jira [BEAM-4107](https://issues.apache.org/jira/browse/BEAM-4107). Original Jira may contain additional context.
Reported by: kenn.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.