When determining expansion service jar, depend on Maven coords instead of Gradle target
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
For example here: https://github.com/apache/beam/blob/release-2.24.0/sdks/python/apache_beam/io/kafka.py#L107
Maven coords is more stable than the Gradle target name so it's better to depend on the prior. See [1] for details.
[1] https://issues.apache.org/jira/browse/BEAM-10986
cc: [~robertwb] [~bhulette] [~kenn]
Imported from Jira [BEAM-11026](https://issues.apache.org/jira/browse/BEAM-11026). Original Jira may contain additional context.
Reported by: chamikara.
Contributor guide
Research direction
Start in sdks/python/apache_beam/io/kafka.py around line 107, then read BEAM-10986 for the Maven-coordinate context. Trace how the expansion service jar is currently selected from the Gradle target. Done means the selection depends on stable Maven coordinates instead of the Gradle target name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100