-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support dependency resolution using coursier #47
Comments
I wonder how much this could speed things up by. It just took 3:32 to run on my relatively simple project with only ~25 dependencies in total (albeit IntelliJ is showing WAY more than that). Perhaps there is something else going on. |
|
I would love for this to be implemented, doing the changes to make this work is actually quite trivial as a result of #86 however as has been posted previously, its currently blocked by coursier/coursier#1790. |
This seems to also use the default resolution mechism in SBT which is Coursier. If so you will hit the same problem mentioned before, coursier cannot get the licenses from all types of dependencies (see coursier/coursier#1790) |
Yes, so I have parse pom.xml manually |
Ah yes I see now. We can do this as a workaround but if you have figured out how to get the proper/full license info maybe it makes sense to fix it in upstream coursier? |
Currently, the plugin resolves the dependencies using ivy resolver. Our builds only work with coursier, therefore we noticed sbt failing to resolve the dependencies.
The plugin seems not maintained anymore. Any pointers on how the plugin could be improved to respect the actual sbt dependency resolution configuration?
The text was updated successfully, but these errors were encountered: