Support replace in DependencyConfiguration.Builder
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 306
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Dependencies needed for the default platform might contain dependencies that are not allowed by the organization consuming Transport plugin. It is not always okay to simply exclude the dependency. Having the flexibility of replacing it with a difference version will be beneficial.
https://github.com/linkedin/transport/blob/2163ec2011d82ec5c1c1f7f3ad27d5e89bfe0cef/transportable-udfs-plugin/src/main/java/com/linkedin/transport/plugin/DependencyConfiguration.java#L54
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in transportable-udfs-plugin/src/main/java/com/linkedin/transport/plugin/DependencyConfiguration.java at the linked Builder code around line 54. Trace how dependencies are currently configured and excluded, then determine where replacement support belongs. Done means the builder can replace a default dependency with a different version without simply excluding it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100