-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to avoid generating versions.properties
?
#640
Comments
Not yet |
Ok, thanks for your very quick response! Should I leave this open to track it or is there already an issue for this? (I couldn't find it) |
This way you can avoid it if you do not use the library notations coming with the plugin: gradle.rootProject {
tasks.configureEach {
if (name == "refreshVersions") {
doLast {
delete("versions.properties")
}
}
}
} |
Or you configure a path for the file that is not version controlled and doesn't disturb like refreshVersions {
file("build/tmp/refreshVersions").mkdirs()
versionsPropertiesFile = file("build/tmp/refreshVersions/versions.properties")
} |
Thanks! I don't know why I didn't think of that. It still feels a bit hacky of course, but better than versioning a comment-only version file. It would be great if the plugin detected that the file doesn't need to be created we there is nothing to write to it |
Any chance this could get some attention? |
Yes, hopefully this year. |
No matter what refreshVersions always generates this file with a latest Kotlin version that screws the build up. Apparently there's no way to disable it: Splitties/refreshVersions#640 So we just put it into the build folder and ignore it
I'm using exclusively the version catalog
libs.versions.toml
, but when runningrefreshVersions
, theversions.properties
file is always regenerated (with nothing but the header comment in it).Is there any way to prevent this?
The text was updated successfully, but these errors were encountered: