Chris Lee

Adding a variant on the "size" use case - where the downstream consumer is an API call it may have constraints on the set of data, such as: * total...

there's an alternate Kotlin syntax for referencing variables where they exist in multiple contexts: [email protected]. In the above it would be [email protected].

Likely related to shadowing issues in #459

#460 removes the shadow plugin as it was not fully applied and causing challenges

happy to contribute code to this, if someone can flip me the contributor deets.

Examples of what is working so far (what isn't visible is all the configuration closures -> Actions, these ones are transformation functions). ``` def "should not fail build when Kotlin...

...as of 1.13.6 the following tasks fail when doing 'release': ``` - Task `:release` of type `pl.allegro.tech.build.axion.release.ReleaseTask`: invocation of 'Task.project' at execution time is unsupported. See https://docs.gradle.org/7.4.2/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution - Task `:verifyRelease`...

@bgalek starting to look through this one. Worked through a simple slice below to illustrate the nature of required changes. Biggest challenge is maintaining VersionConfig compatibility with existing users while...

Looks like this will be clean for Groovy consumers, but not for Kotlin consumers of the plugin: > Note that Gradle Groovy DSL generates setter methods for each Property-typed property...

Excellent. Into this now, it will take a bit to wade through it all.