By the way, it would be nice to be able to have the boxed declarations handle such versions that depend on something else's version automatically... kotlinx serialization's plugin is the same version as Kotlin version...

Boy... I just discovered that when using

includeBuild

in project A to include project B and running refreshVersions task in project A, only project B's versions.properties gets updated 🤕 😧

I would have at least expected that it updates it's own versions.properties... I also wonder from where it resolves versions during a build for project A --- from project A's versions.properties or from project B's 🤔

Hi everyone, i'm unable to update gradle plugin's version. since i can update the version in project build.gradle after running

./gradlew refreshVersionsMigrate

it's replaced by

Android.tools.build.gradlePlugin

with an outdated version.

@louiscad I tried the code in the thread and the

refreshVersions

task on the main project still updates the

versions.properties

in mylib instead of the one in the setting.gradle.kts's path in the main project... is there any workaround?

Hello friends, I've got news! I implemented support for versions catalog: - generating automatically

gradle/libs.versions.toml

- rewriting the files

build.gradle(.kts)

to use them - adding dependency updates in

gradle/libs.versions.toml

It's published in the snapshot version

"0.40.2-SNAPSHOT"

Have a look at the Testing? pargraph from the pull-request https://github.com/jmfayard/refreshVersions/pull/509

i left a few comments in the github issues and PRs but i guess i am still taking soem time to write out what would be important for me (and why i use refreshVersions) in relation to version catalogs first of all.. it is annoying to browse the entire toml file for versions when a plugin might be in

[plugins]

or

[versions]

and a library light have comemnts added by refreshVersion in

[libraries]

or

[versions]

• having

[versions]

on top and folding the other sections closed would be nice can refreshVersions be used to referente accessors to

libs.

? having

implementation(libs.dependency("com.kotlindiscord.kord.extensions:annotations"))

where ``dependency`` would register the dependency and return the reference to

libs.kord.extensions.annotations

(following the grouping rules: versiongroup + name to have a unique key) PS: i have no idea about internals and this might well be impossible.. so please take this as a "wish" but it seems like this could work

fun AbstractExternalDependencyFactory.dependency(dependencyNoation: DepdnencyNotation): Provider<MinimalExternalModuleDependency> {
   val alias = TODO() // register dependency / add to version catalog / generate alias from version-key + artifactname (or just a cleaned up dependency notation if no grouping rules is available)
   // alias = "kord.extensions.annotations"
   return create(alias)
}

unless ofc refreshVersion can make it happen automatically under the hood would something similar be possible in the plugins block too ? there we have to call it like so:

alias(libs.plugin("org.jetbrains.kotlin.jvm"))

maybe ideally the way i use refreshVersion can stay the same.. drop in some dependency in one spot, have refreshVersion deal with adding it to the libraries, versions and whatnot for me. and lastly.. right now it seems like even after migration the toml file contains references to versions with

_

that cause

versions.properties

to be populated it would be nice to be able to fully switch, i assume that is planned those are the features i am hoping for...

If I see a

public const val kotlin_stdlib_jdk8: String = "org.jetbrains.kotlin:kotlin-stdlib-jdk8:_"

in

Libs.kt

, how do I know which version from

version.properties

will be used to replace the

_

? Do I first have to search for

<http://version.org|version.org>_jetbrains_kotlin..kotlin_stdlib_jdk8

and then - if that does not exist - look for variations like

<http://version.org|version.org>_jetbrains_kotlin

or

version.kotlin_stdlib_jdk8

or

version.kotlin

? And do I know which if these will be used if they all exist but have different values?

Been curious about the

kotlin-dsl

plugins in the

buildSrc

directory, any suggestion or ideas for this? https://github.com/jmfayard/refreshVersions/discussions/533

I’ve submitted an issue here: https://github.com/jmfayard/refreshVersions/issues/557 Does it #refreshversions atm not yet supporting 7.4? or maybe is there something else we’ve missed 🙏

Hello I was wondering if it possible to add dependencies in then lib locally. Using buildSrc in my own project. Then once I have noticed that the lib is complete I can of course contribute but since I do not want to wait while Pr is checked and merged (I want to add quite a few libs: Exposed, database drivers, Ktor-server). I have tried add this lib in buildSrc by following the docs, I do not see it. Any ideas?

Bonjour les amis I wanted to add a new page in the website with all the embedded dependency notations. I suffered trying to write html tables inside a markdown file but in the end I think it was worth the effort. 🎉 What do you think? Hint: if you hover on a dependency notation, you can see its dependency name, its version key and its maven coordinate https://jmfayard.github.io/refreshVersions/dependencies-notations/

What could cause

Plugin with id 'de.fayard.buildSrcLibs' not found.

if I configured everything like said in the setup page... even though this is a composite gradle build, it USED to work...?

Bonjour, ever wanted a feature similar to renovabot or dependabot but with refreshVersions? I have been using a Github Workflow to do that for months at work. Here is my guide on how to do it 🙂 https://jmfayard.github.io/refreshVersions/refreshversions-bot/

Hello! I have a dependency in a private repo that requires credentials. So for that dependency I hardcode the version. But then I get this comment above each entry in versions.properties:

## failed to check repo <https://example.com/artifactory/libs-release/> Cause: http status code 403 HTTP 403 Response.error()

Is it possible to configure refreshVersions to skip this repo?

Hi! I just tried upgrading to 0.50.0 and got this error:

Could not find de.fayard.buildSrcLibs:de.fayard.buildSrcLibs.gradle.plugin:0.50.0.

is this a known issue?

Oh... the docs are misleading here... it says to put the pluginManagement block in the buildSrc folder, whereas it needs to be at the root of the project.

The newest update seems to have changed some dependency names... so Android Studio didn't load up the new definitions for some reasons, and code complete was still using the old version even after cleaning the build and .gradle folders a few times... so I had to guess what they were changed to 🙈... it's a good thing there was the new list on the site...

Bonjour les amis! Anyone interested by either... • migrating to Gradle Versions Catalog • or having available dependencies updates automatically show up in

gradle/libs.versions.gradle

? refreshVersions just added support for Gradle Versions Catalog It's a huge feature though, so we would love for gentle early adatopers to give it a try https://github.com/jmfayard/refreshVersions/wiki/RefreshVersions-%E2%99%A5%EF%B8%8F-Gradle-Version-Catalog

Bonjour, if you like my code I write, you may or may not also like the words I write. I let you judge by yourself here -> https://dev.to/jmfayard/why-do-you-have-too-many-tabs-opened-an-almost-imaginary-conversation-with-my-5-years-old-nephew-4721

Good morning folks and thank you for this amazing tool 😄 I have a question regarding Koin. Recently the android related artifacts got a new version of

3.3.0

while the rest of the koin artifacts are on version

3.2.2

. The thing is (for which I haven't found a workaround) that in `versions.properties`file, only a single koin notation gets added. Is there a way to declare those two versions separately other than putting the version myself in the build script?

Probably dumb question. Is there a predefined constant for

kotlin("plugin.serialization")

, and in the interest of teaching me to fish, what’s the easiest way to discover which dependencies have constants already defined?

It seems like refreshVersions doesn't yet know that

.RELEASE

is a higher version than `.RC..`:

version.io.r2dbc..r2dbc-h2=1.0.0.RELEASE
##             # available=1.0.0.RC1

I have 2 questions: • When I run

buildSrcLibs

, it overrides my buildSrc/build.gradle.kts. I have to rollback each time. Is this a known bug? • I have a gradle plugin added to my project hosted in a private maven repository.

refreshVersions

does not add the notation to

Libs.kt

, and the version to

versions.properties

. Is there something I can do about it?

Question... I want to migrate to gradle version catalogs first. then after using it for some time, then we'll update to refresh versions. For the time being... we want to use refreshversions for doing the migration to gradle version catalogs, but it seems like it will always generate a version.properties. Is there anyway to just use refreshVersions for the actual upgrade to version catalogs?

with version 0.60.0 refreshversion stopped working until i added a empty

libs.versions.toml

… also more npm dependencies version keys are incorrectly marked as a unused

i may be missing it, but is the number of comments that are generated? e.g. instead of

employer-profile = "0.1.160"
##            ⬆ = "0.1.162"
##            ⬆ = "0.1.163"
##            ⬆ = "0.1.164"
##            ⬆ = "0.1.165"
##            ⬆ = "0.1.166"
##            ⬆ = "0.1.167"
...
##            ⬆ = "0.1.275"
##            ⬆ = "0.1.276"
##            ⬆ = "0.1.277"
##            ⬆ = "0.1.278"
##            ⬆ = "0.1.279"
##            ⬆ = "0.1.280"
##            ⬆ = "0.1.281"
##            ⬆ = "0.1.282"
##            ⬆ = "0.1.283"
##            ⬆ = "0.1.284"
##            ⬆ = "0.1.285"
##            ⬆ = "0.1.286"

limit it to either

latest

, or

n latest

versions, where ideally n is less than the 126 it currently outputs in this case 🙂 ?

Is there any way to use versionFor() in a plugins block at the root build.gradle.kts in a multi-module project? The IDE gives an error to use an explicit form, and the build just has an Unresolved reference: versionFor...

There seems to be a bug in refreshVersions... I had this problem https://kotlinlang.slack.com/archives/C19FD9681/p1706016947883069 and when I removed the refreshVersions plugin, it was solved...