-
Notifications
You must be signed in to change notification settings - Fork 6
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
Extract list of dependencies from the BOM #13
Conversation
See the context of this feature at heremaps#9 Signed-off-by: Gaël Jourdan-Weil <[email protected]>
Signed-off-by: Gaël Jourdan-Weil <[email protected]>
Signed-off-by: Gaël Jourdan-Weil <[email protected]>
…solver if needed Signed-off-by: Gaël Jourdan-Weil <[email protected]>
@molekyla could you (or someone else) give a look at this PR? The feature would be quite useful to me. |
@gaeljw Sorry for delay. I haven't enough time to test this changes. At the first glance it looks good, but I want to test it on my small project. Will give take a look in a next few day |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contribution. I see no issues related to introduced functionality
Thanks @molekyla . Do you know when this can be part of a release? |
Awesome! Will use it right now then :D |
Solves #9
This adds:
bomDependencies: Seq[ModuleID]
method toBom
instancesBom.dependencies(...)
helper method in the companion object for cases where you only care aboutbomDependencies
but don't need to extract anything else manually from theBom
I've also updated the README with documentation on this new usage and small changes (each in a different commit).
Tests
I've tested this locally using the example described in #9 and it works successfully.
Example
build.sbt
file:Which gives the expected result in terms of versions. Here's a
sbt dependencyTree
extract: