-
-
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
Support plugin versions in version catalog #678
Comments
LouisCAD
changed the title
VersionCatalogOnly mode does not work with plugins
Support plugin versions in version catalog
Mar 15, 2023
Testing a bit further it seemed to me that the plugin always used the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm probably missing something, but just following the docs...:
🐛 Describe the problem
gradle/libs.versions.toml
do not get 'refreshed'VersionCatalogOnly
theversions.properties
is still requiredrefreshVersions
, the versions for plugins in thegradle/libs.versions.toml
do not get comments for the newest versions✅ Expected behavior
VersionCatalogOnly
should only use the version catalog, not theversion.properties
refreshVersions
should refresh plugins as well. It does so in theversions.properties
but this file is not expected at all (How to avoid generatingversions.properties
? #640)💣 Steps to reproduce
settings.gradle.kts
file./gradlew refreshVersionsMigrate --mode=VersionCatalogOnly
./gradlew refreshVersions
gradle/libs.versions.toml
, the versions of plugins are not refreshedversions.properties
file, the build fails (Plugin [id: 'org.springframework.boot'] was not found in any of the following sources
)The text was updated successfully, but these errors were encountered: