that's possible yes. We have a problem currently with KMP projects to find available updates. Maybe a similar issue exists when propagating the versions. How can I reproduce the bug?

I have discovered this website https://libraries.io/ You can search for a dependency and see immediatly its latest release For example https://libraries.io/maven/com.squareup.okhttp3:okhttp It provides an API https://libraries.io/api That could make the experimental update much faster! What do you think @louiscad ?

When you google "gradle dependencies management" you have lots of things already. - The dependencies management on the gradle website, - Spring dependencies management, - .... https://www.google.com/search?q=gradle%20dependencies%20management&safe=off&cad=h

I’m still not sure how to get Gradle plugins inside the

plugins

section to read from the versions file but the

dependencies

versions appear to work well

As I described here: https://github.com/jmfayard/refreshVersions/issues/178 I prepared a bot that is able to apply refreshVersions updates one by one, and opens a pull request to allow semi-automatic management of upgrades. I'm gradually rolling it out on my own projects, and it seems to work well. @louiscad told me that @mbonnin might be interested, so here I am :)

I just tried my first baby-steps but got stuck after the Gradge 6 upgrade. My

settings.gradle

starts with

pluginManagement { repositories { gradlePluginPortal() } plugins { id "org.jetbrains.kotlin.jvm" version "1.3.60" ...

(with proper whitespace) and I could not add the new stuff in there. So I removed the references to plugin

buildSrcVersions

in both

settings.gradle

and

build.gradle

, added

refreshVersions

and

dependencies

to both, and added

buildScript.dependencies.classpath "de.fayard:dependencies:0.5.8"

and the

import

to

build.gradle

. This gets me past the "import" (note: 0.5.8 seems to have changes the layout and I use

import de.fayard.dependencies.DependenciesSetup

) but now I am stuck at

DependenciesSetup.bootstrapRefreshVersionsAndDependencies(gradle.settings)

which fails with "Cannot change the plugin resolution strategy after projects have been loaded." Most likely I painted myself into a corner here...

Can you give more details? What is the error you're seeing?

Hello dear users, I am considering adding config options to refreshVersions, and I'd like your thoughs/feedback on this draft proposal! https://github.com/jmfayard/refreshVersions/issues/202

another question i had, have you considered doing

{key}

for versions (eg:

{react}

) or anything else that is not in maven versions usually that would then lead to a entry

version.react=1.2.3

that would probably not look for updates in maven i find that in kotlin-js-wrappers for example the versions are built out of the versio nand the library they are wrapping, would be cool to use

"{react}-{js.wrappers}"

as version or

npm("react, "^{react}")

refreshVersions

uses

dependencies

internally to find the the available updates and uses that to re-write

Versions.kt

. So unless you want to just see available updates, stick with

refreshVersions

.

consistently across all projects i get a space before

version.ktor=

i wonder whats up with that

tried fiddling with gradle and repository content blocks.. best i can get to work is let gradle tell me that it could resolve a ModuleIdentiefier (

group:name

) on a repository.. true/false but only on repos that have one defined.. and i needed to repimplement some classes because even the most basic stuff is internal or package private in gradle technically i know which code is required to make listing work.. but its all inaccessible from outside

so.. which versions does refreshVerions need to check and display on comments? pretty much just the latest snapshot, release and such right? i am mentioning this because other gradle plugins seem to do this.. they add dependencies with

version = "+"

, resolve them and then compare versions at the very least this will always work

with 1.4.0 coming along a lot of projects have renamed and reshuffled their artifacts eg: coroutine got no runtime anymore just

coroutine-core(-$platform)

for some reason

ktor.client.websockets

is aliased to

"$artifactPrefix-websockets-$native:_"

even on the jvm ?

"io.ktor:ktor-client-websockets:_"

is what i would expect also for some reason refreshVersion did not suggest

1.4.0

for version.kotlin even though its available in the repos

can i somehow use refreshVersions inside

buildSrc

? my usecase is that i need to apply jooq +postgres configurations for a lot of submodules, would be nice to have that done in buildSrc but for that i need the versions

Which syntax would you prefer for dependencies declaration? 1️⃣:

AndroidX.emoji
AndroidX.emoji.appCompat

2️⃣:

AndroidX.emoji
AndroidX.emojiAppCompat

Telling why your prefer on or another choice in this thread can help too 🙂 FYI, the solution number two is the current ont, but please, don't base your choice on what's there currently in refreshVersions.

seems to fail for me when following the setup guide to upgrade: https://scans.gradle.com/s/xk4hbkhyzzalw/failure#1 seems like gradle / idea had the autoimport wrong and still had depednencies cached

the new version actually displays more new versions .. very nice

Is there a way to declare refreshVersions usings plugins block and not adding buildscript block?

is it "safe" to have a composite build included in which i use the

versions.properties

file of the outer project?

bootstrapRefreshVersions(
    listOf(rootDir.parentFile.resolve("buildSrc/dependencies-rules.txt").readText()),
    rootDir.parentFile.resolve("versions.properties")
)

so when there is no errors then everything syncs fine: but if there is even one unrelated error then this happens in idea: i assume that is because idea only then shows the "errors" generated when _ gets rejected is there any way to reduce the severity of those errors or get to the bottom of what the actual cause is ? the errors are also nonsensical:

Cannot resolve external dependency io.ktor:ktor-client-core:{require 1.4.0; reject _} because no repositories are defined.
Required by:
    project :util:paste:pastee
    project :util:paste:pastee > project :module:paste

Possible solution:
 - Declare repository providing the artifact, see the documentation at <https://docs.gradle.org/current/userguide/declaring_repositories.html>

another thing i noticed.. sqldelight duplicates entries in the versions.properties file i have this in there:

plugin.com.squareup.sqldelight=version.sqldelight

...

version.sqldelight=1.5.0-SNAPSHOT

after running the task it changes into

plugin.com.squareup.sqldelight=1.5.0-SNAPSHOT

plugin.com.squareup.sqldelight=version.sqldelight

...

version.sqldelight=1.5.0-SNAPSHOT

btw.. whiy is this a thing and why is refreshVersions not doing it ?

plugins {
    id("com.gradle.enterprise") version "3.4.1"
}

gradleEnterprise {
    buildScan {
        termsOfServiceUrl = "<https://gradle.com/terms-of-service>"
        termsOfServiceAgree = "yes"
    }
}

it seems like a cleaner way to configure.. than importing a function, i assume that plugins there do not provide the same access ?

weird issue caused by refreshVersions: https://scans.gradle.com/s/k4cml4unkop5w/failure#1 but only on github actions, cannot reproduce that locally the project is also quite weird so its possible there is some weirdness going on but since its small enough and does not need updates often i removed refreshVersions

Hello friends gradle refreshVersions has a new website! I put lots of efforts in it and would appreciate some feedback https://jmfayard.github.io/refreshVersions/

refreshVersions might not work out of the box with maven on

gcs://

urls (google cloud storage)

trying to use the gcs thing via jitpack.. on androidStudio it does not work at all.. a different dependency seems to help but then it runs into the issue of not recognizing version in a non android project i tried it and it seems to wrk.. but this error gets thrown:

org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':refreshVersions'.
Caused by: java.lang.IllegalArgumentException: Cannot get version candidates with an empty fetchers list.

do i HAVE to use

dependencies {
    classpath("com.android.tools.build:gradle:_")
    classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:_")
  }

instead of

plugins {
    id("com.android.application")
    id("com.android.library")
}

with pluginManagement ? is that already a known issue ?

yeah there migth be a small issue with gcs support.. and that is.. it might override versions of guava and other google libs that then fail at runtime when loading the plugin i have this error

Caused by: java.lang.NoSuchMethodError: com.google.common.collect.ImmutableList.toImmutableList()Ljava/util/stream/Collector;
	at com.android.build.gradle.internal.TaskManager.<init>(TaskManager.java:371)

not sure if thats the cause.. or not but it is weird