adenhartog

It probably concerns this line: https://github.com/allegro/axion-release-plugin/blob/6f89fdd9e1807cea86ac5a86450e4f97101e1549/src/main/groovy/pl/allegro/tech/build/axion/release/domain/BaseExtension.groovy#L23 For ease of use, the gradle link from the warning message: https://docs.gradle.org/8.4/userguide/upgrading_version_7.html#for_use_at_configuration_time_deprecation

Sure. Judging from the comment above the linked line, the offending method call should be removed and then the unit tests should be fixed. I would guess the ideal fix...

@bgalek When removing the offending method call one example of the failing tests is `RepositoryConfigFactoryTest` with `java.lang.IllegalStateException: Cannot obtain value from provider of Gradle property 'release.customKeyPassword' at configuration time. Use...

Another option would be to not have a convention based on a Gradle property at all. This would mean the user would have to set the property in a buildscript...

We found the following workaround (gradle kotlinscript style): ` tasks.withType { doNotTrackState("Workaround for gradle 8") } `

This issue occurs when the axion plugin is applied in the root project, as the manual says you should always do, and which is in line with my own experiences....

I am aware and did that.

I hope to find some time to do that this week.

I cloned the repo and the currentVersion task already fails on my system. ``` $ g cV > Task :app:currentVersion FAILED FAILURE: Build failed with an exception. * What went...

It was `.gradle\8.0.2\checksums\checksums.lock`