Skip to first unread message
Robin Green
Aug 6, 2012, 4:48:57 PM8/6/12
to simple-b...@googlegroups.com
I've just quickly hacked together an sbt plugin to suggest dependencies that are missing from your sbt build files, given imports that can't be found:
https://github.com/greenrd/sbt-autodeps
It's not terribly useful at the moment, but I've added some TODOs to the issue tracker to indicate how I think it could be made more helpful.
I suppose a slight downside of using this plugin is you might then opt for the easy option of using the same version of a dependency that you (or someone else) used in a previous project, without checking to see if a newer version of the dependency has been released since then. But taking into account concerns about new versions breaking things and so on, that might actually be considered a good thing in some cases!
https://github.com/greenrd/sbt-autodeps
It's not terribly useful at the moment, but I've added some TODOs to the issue tracker to indicate how I think it could be made more helpful.
I suppose a slight downside of using this plugin is you might then opt for the easy option of using the same version of a dependency that you (or someone else) used in a previous project, without checking to see if a newer version of the dependency has been released since then. But taking into account concerns about new versions breaking things and so on, that might actually be considered a good thing in some cases!
eugene yokota
Aug 6, 2012, 6:30:40 PM8/6/12
to simple-b...@googlegroups.com
Hi Robin,
> FIXME
If the main use case is to use it as a global plugin, wouldn't it be better to implement a command that automatically gets installed?
I did that for sbt-man. If you want `man` command you get it for every build. But no changes to the build.sbt is required at the project level.
If the build author adds reference to sbt-autodeps from build.sbt, the build won't compile for other users without the global plugin.
-eugene
Reply all
Reply to author
Forward
0 new messages