Investigate methods of moving dependency downloads to configurations
Nobody has claimed this yet.
- #90 by @jpenilla — closed without merging
- Dominant language
- Kotlin
- Stars
- 317
- Forks
- 76
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 5
Description
For simplicity and to just get paperweight working I have dependencies downloading in tasks using a download service that I copied from the download-task plugin. This works fine but isn't able to cache as well as Gradle's built-in dependency system.
There's some issues which makes this not a terribly straight-forward thing to do, but I have some ideas now that I've learned more about Gradle on how I can actually do this successfully. Not guaranteed though.
Contributor guide
No contributing guide indexed for this repository
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
Review the existing task-based download service and the issue's ideas for moving dependencies into Gradle configurations. Confirm whether this can preserve paperweight downloads while using Gradle's built-in dependency caching; no files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100