{"push_id":1108245124,"size":1,"distinct_size":1,"ref":"refs/heads/so-plugins-subprojects","head":"4bde45b4d3049bc63cd0ca8994bfd69897057801","before":"9353c2b1e98b79245cb4f0e1b3f5c8ca2887ac45","commits":[{"sha":"4bde45b4d3049bc63cd0ca8994bfd69897057801","author":{"email":"eb0877843acc39f8ef6f7269937dee931c372d23@gradle.com","name":"Stefan Oehme"},"message":"Allow applying plugins to subprojects using new DSL\n\nThis change adds new `subprojects` and `allprojects` methods to the `plugins`\nDSL, which allow users to apply plugins to multiple subprojects at once.\n\nThe plugins are resolved in the context of the parent project and put on\nthe parent's classpath. This ensures that the parent can cross-configure its\nchildren. A side-effect is that unrelated subprojects will see those plugin\nclasses too, even though they are not applied to them.\n\nThe `plugins` block is no longer backed by an AST transformation, but is\nnow compiled, exactly like the `buildscript` and `pluginRepositories` blocks.\nThis will give users greater flexibility to conditionally apply plugins in the\nfuture. Currently no access is granted to any methods outside of the `plugins`\nAPI though.","distinct":true,"url":"https://api.github.com/repos/gradle/gradle/commits/4bde45b4d3049bc63cd0ca8994bfd69897057801"}]}