Feedback on Gradle Versions Catalog support?

[jmfayard]

We have released in 0.50.0 support for Gradle Versions Catalog support.

--> See https://jmfayard.github.io/refreshVersions/CHANGELOG/

This is a new and huge feature so we need you to test it out and provide feedback.

1. Update Gradle with ./gradlew wrapper --gradle-version 7.5.1 (Versions Catalogs are stable since Gradle 7.4)
2. Setup refreshVersions 0.50.+ in your build in its latest release (our support for Versions Catalog is very new).
3. Run ./gradlew refreshVersionsMigrate --mode=VersionCatalogAndVersionProperties
4. See the generate catalog at gradle/libs.versions.toml
5. See your git diff to check how your build has been migrated

Read the friendly documentation here

Thanks for your help!

[jmfayard]

Issue found here #396 (comment)

Extension of type 'VersionCatalogsExtension' does not exist. Currently registered extension types: [ExtraPropertiesExtension]
Gradle 7.5.1 and refreshVersions 0.50.0

EDIT Fixed in 0.50.1
https://jmfayard.github.io/refreshVersions/CHANGELOG/

[mcpiroman]

Hi, I migrated from buildSrc directly to VersionsCatalogOnly and then refreshVersions also generates a new versions.properties, which I don't use (because there is no point to use both?).

[jmfayard]

Hello I guess this will be a frequent question. There are multiple partuak answers.

Here is a short summary:

• I agree in principle but Rom was not built in one day
• you can make the file less visible by diffusing refreshVersions to put the file under gradle/versions.properties
• personally I think that refreshVersions dependency notations are a better (complementary) solution for common libraries

See if this answer your questions here

https://github.com/jmfayard/refreshVersions/wiki/RefreshVersions-%E2%99%A5%EF%B8%8F-Gradle-Version-Catalog#faq-are-you-giving-up-on-the-versionsproperties-file-

[myjohndoeside]

So, currently this plugin could not work without versions.properties file?

[jmfayard]

Currently yes.
Cause that's how refreshVersions work from the start and from before versions catalog.

[imashnake0]

Just merged a branch that I was using to try out the feature. It works flawlessly!

P.S. Sorry I haven't been able to contribute lately, had a lot on my plate 😭

[jmfayard]

I'm glad to hear! Le jeu. 13 oct. 2022 à 07:14, Kamalesh ***@***.***> a écrit :

…

Just merged a branch that I was using to try out the feature. It works flawlessly! <imashnake0/Animite@6192701> . P.S. Sorry I haven't been able to contribute lately, had a lot on my plate 😭 — Reply to this email directly, view it on GitHub <#592 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADQFSCXQP735MZRXLKL5IDWC6LDZANCNFSM6AAAAAAQG5YP5Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[Arc-E-Tect]

I like the fact that Version Catalogs are now supported. Took me a while before I had the time to switch and check this new feature.

I noticed that none of the --mode flags process the plugins section in the TOML file. libraries are processed and an _ is put in place of the version, but with plugins this is not the case. I need to manually replace the version strings with an _ after that all still works.

[Commodore68]

Gotta give you kudos for this! being able to use this to migrate to version catalogs was great. Even for a multi-module gradle project that makes heavy use of build-src. The semi-automatic migration was very helpful for dependencies in my main modules.

Then it was just a matter of figuring out how to migrate the things in my build-src over to the version catalog, which I was able to do with a minimal amount of code.

only minor issue I had, was that I had some dependencies using a gradle extension variable in kts build scripts to set versions and the auto migrate did not replace those with _

val versionVariable: String by rootProject.extra //OR val versionVariable: String by project

implementation("group:name:$versionVariable")

great work again.