Skip to content
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 custom non-toml version catalogs configured through settings.gradle[.kts] #6838

Open
1 task done
lbenedetto opened this issue Mar 14, 2023 · 0 comments
Open
1 task done
Labels
L: java:gradle Maven packages via Gradle T: feature-request Requests for new features

Comments

@lbenedetto
Copy link

lbenedetto commented Mar 14, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

After #6249 version catalogs defined in toml files are supported.

But version catalogs can also be configured directly inside the gradle file

dependencyResolutionManagement {
    versionCatalogs {
        create("libs") {
            version("version.id", "1.0")
            library("library.id.one", "group", "name").versionRef("version.id")
            library("library.id.two", "group", "name").version("2.0")
        }
    }
}

Would be nice if Dependabot could also handle this situation.

I do not believe this would need to depend on #1164, it should be enough to just parse the file on its own, handling it like it's a toml file but with different syntax.

Related:

@lbenedetto lbenedetto added the T: feature-request Requests for new features label Mar 14, 2023
@jeffwidman jeffwidman added the L: java:gradle Maven packages via Gradle label Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: java:gradle Maven packages via Gradle T: feature-request Requests for new features
Projects
None yet
Development

No branches or pull requests

2 participants