PoC of using gradle to obtain classpath for dependency expressed in config #137
Conversation
|
For reference, here's output for fetching gradle-api: This showcases mostly how quickly very large those dependency trees can become. And basically we can take that classpath and feed it into our other tool invocations as additional path - getting us out of jar-hell 👍
|
| } | ||
| } | ||
| """); | ||
| } |
There was a problem hiding this comment.
Silly trick, but effective ¯_(ツ)_/¯
We could implement the same methods with more direct raw APIs eventually but this gets us going and tbh gets the job done well enough. It would also integrate well with targeting a real build.gradle so we can share dependencies with a real build definition, and not re-declare them for swift in a different place again if a project is using gradle anyway.
|
I'll revive this soon, after converging plugins a bit more. |
|
Completed in #191 |
PoC of the necessary infra for #135
Brought the PoC to a place where I can leave it for a moment before I get back to it.
This allows us to: use gradle as an API to resolve and fetch dependencies, and return a classpath containing them.
Usage like this:
Problems to solve: