-
Notifications
You must be signed in to change notification settings - Fork 502
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
Extract dependencies from Gradle Version Catalogs #3534
Labels
Comments
I've a WIP branch for this feature at https://github.com/scala-steward-org/scala-steward/compare/topic/gradle-version-catalog |
fthomas
added a commit
that referenced
this issue
Jan 13, 2025
This adds partial support for Gradle builds that use a [version catalog](https://docs.gradle.org/current/userguide/version_catalogs.html) (i.e. a `gradle/libs.versions.toml` file). Dependencies are extracted from the version catalog just by parsing the `libs.versions.toml` file. Since the version catalog only contains libraries and no resolvers, the default resolver is used for the `Scope` of these libraries. This is one reason why this Gradle support is only partial. The other is that additional dependencies and plugins that are defined in other Gradle build files are also ignored. Closes: #3534
fthomas
added a commit
that referenced
this issue
Jan 13, 2025
This adds partial support for Gradle builds that use a [version catalog](https://docs.gradle.org/current/userguide/version_catalogs.html) (i.e. a `gradle/libs.versions.toml` file). Dependencies are extracted from the version catalog just by parsing the `libs.versions.toml` file. Since the version catalog only contains libraries and no resolvers, the default resolver is used for the `Scope` of these libraries. This is one reason why this Gradle support is only partial. The other is that additional dependencies and plugins that are defined in other Gradle build files are also ignored. Closes: #3534
fthomas
added a commit
that referenced
this issue
Jan 16, 2025
This adds partial support for Gradle builds that use a [version catalog](https://docs.gradle.org/current/userguide/version_catalogs.html) (i.e. a `gradle/libs.versions.toml` file). Dependencies are extracted from the version catalog just by parsing the `libs.versions.toml` file. Since the version catalog only contains libraries and no resolvers, the default resolver is used for the `Scope` of these libraries. This is one reason why this Gradle support is only partial. The other is that additional dependencies and plugins that are defined in other Gradle build files are also ignored. Closes: #3534
fthomas
added a commit
that referenced
this issue
Jan 17, 2025
This adds partial support for Gradle builds that use a [version catalog](https://docs.gradle.org/current/userguide/version_catalogs.html) (i.e. a `gradle/libs.versions.toml` file). Dependencies are extracted from the version catalog just by parsing the `libs.versions.toml` file. Since the version catalog only contains libraries and no resolvers, the default resolver is used for the `Scope` of these libraries. This is one reason why this Gradle support is only partial. The other is that additional dependencies and plugins that are defined in other Gradle build files are also ignored. Closes: #3534
fthomas
added a commit
that referenced
this issue
Jan 17, 2025
This adds partial support for Gradle builds that use a [version catalog](https://docs.gradle.org/current/userguide/version_catalogs.html) (i.e. a `gradle/libs.versions.toml` file). Dependencies are extracted from the version catalog just by parsing the `libs.versions.toml` file. Since the version catalog only contains libraries and no resolvers, the default resolver is used for the `Scope` of these libraries. This is one reason why this Gradle support is only partial. The other is that additional dependencies and plugins that are defined in other Gradle build files are also ignored. Closes: #3534
fthomas
added a commit
that referenced
this issue
Jan 17, 2025
This adds partial support for Gradle builds that use a [version catalog](https://docs.gradle.org/current/userguide/version_catalogs.html) (i.e. a `gradle/libs.versions.toml` file). Dependencies are extracted from the version catalog just by parsing the `libs.versions.toml` file. Since the version catalog only contains libraries and no resolvers, the default resolver is used for the `Scope` of these libraries. This is one reason why this Gradle support is only partial. The other is that additional dependencies and plugins that are defined in other Gradle build files are also ignored. Closes: #3534
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Gradle has Version Catalogs which are lists of dependencies in
gradle/libs.versions.toml
files which Scala Steward could easily extract dependencies from and therefore partially support Gradle builds. A Version Catalog does not include resolvers, so in a first step Scala Steward would only use the default resolver to look for new versions.The text was updated successfully, but these errors were encountered: