Introduction: Gradle dependencies with IDE integration and lookup for available updates
More: Author   ReportBugs   OfficialWebsite   

//include::includes.adoc[] :plugin_version: 0.3.2 :repo: jmfayard/buildSrcVersions :branch: 26-buildSrcVersions :github:{repo} :plugin_issues: :plugin_gradle_portal: :gradle_kotlin_dsl: :gradle_guide_new: :gradle_guide_buidllogic: :medium_puzzle: :medium_protips: :medium_mvp: :devto_readme: :root: file:///Users/jmfayard/Dev/mautinoa/buildSrcVersions :issues: :master: :badge_mit: image:["GitHub",link="{github}/blob/master/LICENSE.txt"] :badge_version: image:["Maven Central",link=""] :badge_issues: image:{repo}.svg["GitHub issues",link="{github}/issues"] :badge_pr: image:{repo}.svg["GitHub pull requests",link="{github}/pulls?utf8=%E2%9C%93&q=is%3Apr+"] :badge_build: image:{repo}/{branch}.svg["Travis (.org)",link="{repo}"]

//:imagesdir: /Users/jmfayard/Dev/mautinoa/buildSrcVersions/doc :imagesdir: doc

= buildSrcVersions

{badge_version} {badge_build} {badge_mit} {badge_issues} {badge_pr}

[[img-libs]] image::Libs.gif[title="IDE integration when you put your dependencies information in the buildSrc",alt="IDE Integration", link="{master}/doc/Libs.gif"]

Gradle has a special module called buildSrc where you can put Kotlin code and make it directly available to all your Gradle build files.

This is better than the traditional solution of putting your global variables in a Gradle ext property or in a Groovy HashMap, because in that case, the IDE support is exactly what you would expect when you work with an HashMap.


Now, what is better than writing manually those files link:doc/Versions.kt[Versions.kt] and link:doc/Libs.kt[Libs.kt]?

Having a Gradle plugin write them for you maybe?

== Prerequisites

  • Kotlin, JVM and Android projects.
  • Gradle 4.3+ and Gradle 5.0+
  • The IDE integration works in IntelliJ >= 2008.03+ and Android Studio 3.2+.
  • The IDE integration works for both build.gradle (Groovy) and build.gradle.kts (Kotlin) files.

== Installation

Edit your root build.gradle(.kts) file

buildscript { //... } plugins { id("de.fayard.buildSrcVersions") version "{plugin_version}" }

// Don't put any code before the buildscripts {} and plugins {} block

== Extract your dependencies

The plugin adds a task to your build, also called :buildSrcVersions. Run it like this:

$ ./gradlew buildSrcVersions
> Task :dependencyUpdates
> Task :buildSrcVersions
        new file:   buildSrc/build.gradle.kts
        new file:   buildSrc/.gitignore
        new file:   buildSrc/settings.gradle.kts
        new file:   buildSrc/src/main/kotlin/Libs.kt
        new file:   buildSrc/src/main/kotlin/Versions.kt

Synchronize your Gradle build and you can start to replace your magic strings:

dependencies {

== Search for dependencies updates

Upgrade dependencies tend to be tedious but it is critically important:

  • Few projects have versioned documentation: master/ is their documentation. This means you can waste time trying out snippets that do not work in the version you are using.
  • When you open an issue, you will often be asked: Can you reproduce this problem in the latest version?

This plugin inherits from[Ben Manes's Versions plugin] the feature to automatically determine which dependencies have updates.

When you decide you want to update some dependencies, run again the plugin:

$ ./gradlew buildSrcVersions
> Task :dependencyUpdates
> Task :buildSrcVersions
        modified:   buildSrc/src/main/kotlin/Libs.kt
        modified:   buildSrc/src/main/kotlin/Versions.kt

The file Versions.kt is regenerated with a comment indicating which new version is available.

object Versions {
    val moshi = "1.8.0"
    val com_squareup_okhttp3 = "3.11.0" // available: "3.12.0"

[[img-versions]] image::Versions.gif[title="buildSrcVersions search for dependencies updates and let you decide which you want to apply",alt="IDE Integration", link="{master}/doc/Libs.gif"]

As shown in this screencast:

  • To update, just delete the part "3.11.0" // available .
  • Remove the comment if you don't want to update.

== FAQ

Questions? {issues}[Look at the existing issues], then ask your own.

[[FAQ]] image::FAQ.png[title="FAQ",alt="IDE Integration", width="600", link="{issues}"]

== Changelog

See {master}/[]

The project was called gradle-kotlin-dsl-libs before, which was a bad name for reasons explained in {issues}/26[#26]

== Contributing

  • This project is licensed under the MIT License. See {master}/LICENSE.txt[LICENSE.txt]
  • Explain your use case and start the discussion before your submit a pull-request
  • Please read {master}/[] the process for submitting pull requests to us.

== Acknowledgments[Gradle] and[JetBrains] have made this plugin possible by working on improving the IDE support for Kotlin code from the buildSrc module.

This plugin embraces and extends[Ben Manes's wonderful "Versions" plugin].

The Kotlin code generation is powered by[Square's Kotlinpoet]

Support Me
About Me
Google+: Trinea trinea
GitHub: Trinea