Can I avoid the use of the built-in dependency notation?

[podollb]

Is there a way to avoid the use of the built-in dependency notation? If I have existing versions.properties files and/or new projects that I want to migrate to refreshVersions, but I do NOT want to use the built-in dependency notation, is there a flag I can set to do that?

https://splitties.github.io/refreshVersions/dependency-notations/

[LouisCAD]

Yep, just use _ in place of the version, as all documented on this page: https://splitties.github.io/refreshVersions/add-dependencies/

[LouisCAD]

You are not scanning dependencies added by Gradle plugins with this technique, FYI.

Can you give a bit more information about the kind of automation that requires this data, the use case you have?

[podollb]

The kind of automation, at the basic level, is simple text parsing of build.gradle.kts files.

[LouisCAD]

That's not telling why you are parsing those files.

I'm asking because there might be better solutions than what you're asking for.
For example, there's this Gradle plugin that suits several dependency tracking related use cases.

[podollb]

Sorry for being vague, but there are a few types of automation tools that parse the build.gradle.kts files (across many git organizations and repositories) to glean information (for the most part, it's simply being treated, and seen, as a text file -- gradle is not involved).

[LouisCAD]

Forgot to link the Gradle plugin I was referring to: https://github.com/dropbox/dependency-guard