The following dependencies exceed the version found at the milestone revision level: The following dependencies are using the latest milestone version: : Project Dependency Updates (report to plain text file) gradlew dependencyUpdatesĪnd it should produce project dependency report that looks like this:. Once added to your gradle file, you just do: $. Gradle Versions Plugin can create reports in human readable plain text form, but can also dump it as JSON or XML which is pretty useful for automated/scripted processing. Note that it appears you must have the inspection enabled in order to run it manually - so (as of Android Studio 2.0 Beta 2) you need to find the inspection in settings, enable it, then run it by name, then disable it again (to regain previous performance).Īside from the Android Studio's built-in feature, there's nice gradle plugin called Gradle Versions Plugin that does exactly what you want, with the benefit of being plain gradle extension, which means being not bond to any IDE - just pure Gradle thing. If you're on an old version (you should update) the following may help: Then search for "Newer Library Versions Available", and run it on your module.Įdit: The above should just work as of Android Studio 2.3. This is similar to the GradleDependency check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also much slower.īecause of the slowdown this can introduce I'd recommend running it manually periodically, rather than having it always on. This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project. Settings > Editor > Inspections > "Newer Library Versions Available" This is now built-in to Android Studio as a Lint check.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |