Update information is obtained from the maven metadata.
There is also a limited support for Ivy repositories hosted on BinTray.
If your project uses crossScalaVersions you will be presented only with updates available for all scala versions.
Requirements
sbt 0.13.9 and later. sbt 1.x is supported since version 0.3.1.
Installation
Stable version
Create a ~/.sbt/1.0/plugins/sbt-updates.sbt file (for sbt 1.x series), or ~/.sbt/0.13/plugins/sbt-updates.sbt (for sbt 0.13.x series) with the following content:
Choose one of versions available on Sonatype. Then create a ~/.sbt/1.0/plugins/sbt-updates.sbt file (for sbt 1.x series), or ~/.sbt/0.13/plugins/sbt-updates.sbt (for sbt 0.13.x series) with the following content:
It is preferred to use sbt-updates as a global plugin. Nevertheless, there might be cases when you want to use sbt-updates
as a project plugin. In that case, add the plugin definition to project/sbt-updates.sbt. You can then use dependencyUpdates
target to find updates for your project. But this way you won't be able to check sbt plugin updates. In order to check both
dependency updates and sbt plugin updates, add the plugin to both project and meta project i.e project/sbt-updates.sbt
and project/project/sbt-updates.sbt and run:
sbt-updates relies on the repository Maven metadata. If you want to get update notifications
for artifacts published by other sbt projects, you should ensure that metadata is updated
correctly. One possible way to achieve this is to use sbt-aether-deploy.
Example
In order from left, the result shows current version, patch update version, minor update version and major update version.
请发表评论