This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Idiomatic JVM See the new document at https://docs.google.com/document/d/1H23PyaUQzPrRyKGMoOCsvfsSTtHi8agmWv-Q58TtFUg/edit?usp=drivesdk

Plugin receives build result See the new document at https://docs.google.com/document/d/1nS1JTwdCMQN_0WaaFrSUxoQOj3zOqmKmXxC6k0OXUR0/edit?usp=drivesdk

This message was deleted.

This message was deleted.

Specification: Configuration Roles Changes in Gradle 8.1https://docs.google.com/feeds/vt?gd=true&id=1vBWyHSaUYHUlh8Xs7lWC1asGv4z8ww0F_qAjhKBC8h8&v=21&s=AMedNnoAAAAAY-qwcVhc3xqn2xhMvpo4lR4PIOpjBsq7&sz=s220 See the new document at https://docs.google.com/document/d/1vBWyHSaUYHUlh8Xs7lWC1asGv4z8ww0F_qAjhKBC8h8/edit?usp=drivesdk

GBT - Design Spechttps://docs.google.com/feeds/vt?gd=true&id=12Y37SXQFBVKdU6mPKMxy5Rnj_MI2TX4ipY-UG-IBnzU&v=1&s=AMedNnoAAAAAY-xkOCHdq3lVJoviwzAgJtm8LZSCtRpQ&sz=s220 See the new document at https://docs.google.com/document/d/12Y37SXQFBVKdU6mPKMxy5Rnj_MI2TX4ipY-UG-IBnzU/edit?usp=drivesdk

The above design spec is on Defining a Local Variant.

New Design Spec: Easier Plugin Dependency Declaration https://docs.google.com/document/d/1P7aTeeVNhkhwxcS5sQNFrSsmqJOhDo3G8kUdhtp_vyM/edit Problem In order to declare the dependency on a Gradle plugin in a dependencies block, one currently needs to provide either the plugin module coordinates or the plugin marker coordinates, e.g. "$pluginId:$pluginId.gradle.plugin:$pluginVersion". It is not documented how to do so and it is awkward to look up those coordinates from the plugin portal. It is currently not possible to declare a dependency on a plugin by reusing the plugin identifier that is commonly used when applying it. There is no translation from this id to the coordinates, nor is it possible to use the version catalog when declaring a dependency on a plugin. Proposal Allow the declaration of dependencies on plugins using their id (and version) or the version catalog.

New Design Spec: Encrypting Configuration Cache State files The configuration cache stores user data, which may contain sensitive information (passwords, keys, etc). We need to provide a reasonable solution for the short term (8.1). This is a proposal for implementing support for optional encryption of those files in the configuration cache area that are meant to hold user data. Why Customers manifested concerns with Configuration Cache being promoted for wide adoption while it may store potentially sensitive information in plain text. We need a short term solution (8.1 timeframe) that will cover existing builds, not only new builds.