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

Possibility to exclude dependencies from hardcoded recognition #665

Open
Vampire opened this issue Feb 6, 2023 · 0 comments
Open

Possibility to exclude dependencies from hardcoded recognition #665

Vampire opened this issue Feb 6, 2023 · 0 comments

Comments

@Vampire
Copy link
Contributor

Vampire commented Feb 6, 2023

If I for example have a conventions plugin project using `kotlin-dsl` plugin, it should have the version embedded in Gradle.
You usually do not declare that version in some centralized place, but use the `kotlin-dsl` plugin accessor that has the matching version indeed hard-coded.

The same for dependencies that should use the embeddedKotlin version of Gradle.

And also if you includeBuild a build and depend on it.

All these are shown as hardcoded versions in the task result and it suggests to use refreshVersionsMigrate.

A facility (unless I just missed it) to configure those dependencies that are ok to be hardcoded would be nice to see if really a hardcoded one is added. Also because it says there are 13 hard-coded versions (which seems to be too much for that project) and only the first three are shown.

@Vampire Vampire changed the title Possibility to exclude dependencies from hard-coded recognition Possibility to exclude dependencies from hardcoded recognition Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant