Long term plan: focus on refreshVersions

The long-term plan for v1.0 is to focus on :refreshVersions instead of :buildSrcVersions

refreshVersions

Starting from release 0.8.0 the plugin is now called and contain only the task refreshVersions

plugins {
  id("de.fayard.refreshVersions").version("0.8.x") // or newer
}

buildSrcVersions

We are not quite ready yet to extract the useful parts of buildSrcVersions to another plugin, so if you need the features from buildSrcVersions, stay with this for now:

plugins {
  id("de.fayard.buildSrcVersions").version("0.7.0")
}

Next step

The file buildSrc/src/main/Libs.kt is still useful right now, but I am working on a better solution in collaboration with this project

https://github.com/LouisCAD/Splitties

Later plans

• rename the project, making sure that the URLs still work
• rename the extension name from buildSrcVersions { ... } to refreshVersions { ... }
• have a minimialist plugin that focus on :refreshVersions
• keep the plugin buildSrcVersions for my existing users who need their current features

[LouisCAD]

Actually, Splitties is moving to be a multiplatform project (although the biggest work I did there hasn’t made it to a non dev release yet), so I’d make the plugin not target just Android in the near future.

That said, it might make sense to have a backend focused plugin for the popular dependency constants, which might or might not be in Splitties.

[jmfayard]

@DanySK Yes, that’s the plugin com.louiscad.splitties plugin that we are working on here https://github.com/LouisCAD/Splitties/tree/develop/plugin/src/main/kotlin/com/louiscad/splitties

This plugin is for Android dependencies. I think I will do later a plugin for backend/JVM libraries later