From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

If I understand correctly, I think using `addProvider()` instead of `add()` can help you. Then you can determine the version lazily (i.e. late) in the configuration phase.

<@UAFGSU86M> wrote a detailed post about this topic:
<https://melix.github.io/blog/2022/03/gradle-conditional-dependencies.html>

hmmm I read the article, played a bit with `addProvider` /
```add("kspCommonMainMetadata", provider { "com.example:${version}" })```
 etc, but I don't think that's the problem. When this gradle plugin is used in a project, things like `version`, `project.ersion` / `rootProject.version` don't apply to the plugin, but rather to the project that applies it. Is there anything that holds the plugin version?

this seems to be related: <https://discuss.gradle.org/t/how-can-a-custom-gradle-plugin-determine-its-own-version/36761/2> will check

Sorry, I misunderstood what you are trying to achieve.

the article you sent was very interesting anyway. gave me some insight, but tbh I still can't figure out the "lifecycle" of gradle plugin, e.g. tried using the Providers for resolving extension parameters but eventually I end up using afterEvaluate every time :shrug:

Yes it can be challenging, in particular because the Provider/Property API is not yet used consistently in many plugins and Gradle itself. :neutral_face:
Usually it is possible to do for almost all thing by now (I think) but I can understand that it is frustrating if it is too hard to figure out and you then use `afterEvaluate` because it is just more straight forward to use for some cases.