Question I want to migrate to gradle version catalogs first

Question

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

jmfayard · Answer

jmfayard · Answer

I think it s `` gradlew refreshVersionsMigrate mode=VersionCatalogAndVersionProperties` I m launching my own company so it s hard to maintain things right now

Colton Idle · Answer

Yeah I did that but it still generates a version properties in addition to the toml

Vampire · Answer

It always will

Colton Idle · Answer

even with VersionCatalogOnly it still does

Vampire · Answer

Yes it always will

Colton Idle · Answer

but yeah this is so close to what i need im surprised theres not a proper converter to version catalogs but maybe im just naive

Vampire · Answer

I forgot why but there was some situation where you would still need it If you don t you can configure it to be created in a volatile spot

Vampire · Answer

One moment I ll show you what I did

Vampire · Answer

```conditionalRefreshVersions work around for file build tmp refreshVersions mkdirs work around for versionsPropertiesFile = file build tmp refreshVersions versions properties ```

Vampire · Answer

Ah the linked issue mentions the case If you use the dependency notations coming with the plugin they are defined with ` ` version and thus need the `version properties`

Colton Idle · Answer

Hm not exactly sure where that leaves me but i suppose i will just try to do this manually instead

Vampire · Answer

Those <https jmfayard github io refreshVersions dependency notations > If you use them you need the `version properties` If you don t use them I don t you can configure away the file

Colton Idle · Answer

oh so I can use the configuration block of refreshVersions to not use those let me try that

Vampire · Answer

Other way around If you don t use them you don t need the version properties file and thus can configure it to be generated in the tmp directory where it does not disturb

Colton Idle · Answer

Yeah but it still updates all of my build files to use them e g My build files now use instead of

CLOVIS · Answer

I just ` gitignore` the empty version properties file

Vampire · Answer

Also a possibility but I prefer it to not clutter my view D

Vampire · Answer

gt Yeah but it still updates all of my build files to use them Even with `VersionCatalogOnly` I didn t use the migration so far

Colton Idle · Answer

Yep

Vampire · Answer

Then I would say that is a bug gt ``` Mode VersionCatalogOnly gt gt Use the default versions catalog for all the dependencies and their versions + gt ignoring built in dependency notations gt ```

Colton Idle · Answer

Cool Thought it was just me