Replies: 7 comments 3 replies
-
Issue found here #396 (comment)
EDIT Fixed in 0.50.1 |
Beta Was this translation helpful? Give feedback.
-
Hi, I migrated from buildSrc directly to VersionsCatalogOnly and then |
Beta Was this translation helpful? Give feedback.
-
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 😭 |
Beta Was this translation helpful? Give feedback.
-
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>
|
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
In my experimental project
If I delete the version.properties it doesn't build, but as far as I can see the versions are now hard-coded in the toml? |
Beta Was this translation helpful? Give feedback.
-
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.
./gradlew wrapper --gradle-version 7.5.1
(Versions Catalogs are stable since Gradle 7.4)./gradlew refreshVersionsMigrate --mode=VersionCatalogAndVersionProperties
gradle/libs.versions.toml
git diff
to check how your build has been migratedRead the friendly documentation here
Thanks for your help!
Beta Was this translation helpful? Give feedback.
All reactions