-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor code to make it possible to use with Boot #7
Comments
It's possible a bit of it could be rewritten to use pomengranate (the underlying wrapper around the Aether/Maven code) more directly; that would make it more reasonable to have Boot make use of the code. To be honest, it's a bit of a hack getting the dependencies, especially the full dependency tree. |
There's also a few other things related to logging that are a bit Leiningen specific but that could be refactored (we pass around an options map everywhere, logging could be abstracted to functions added to the options map). |
So maybe steps towards boot compatibility would be:
For context, I know boot has some facilities around dependencies like
Note: I did not dig into the vizdep code yet so it may not all make sense - or make sense at all. |
I don't use Boot any more (I tend to use Joker where in the past I used Boot). I'm open to a reasonable PR to break the code up to be more easily leveraged by Boot, but don't have the bandwidth to do the work itself. |
I get this is a leiningen task.
I am sure there are people using boot that would be interested (I am one).
This project could either provide a boot task, or expose functions that a boot task could use to render the graph, prune dependencies etc.
The text was updated successfully, but these errors were encountered: