plugins { id("xxx") }
See original GitHub issueIs there a way to use the new plugins syntax instead of bulidscript?
That makes for a much better user experience when working with the gradle kotlin dsl.
plugins {
id «plugin id» version «plugin version»
}
See the information about the new plugin mechanism in this page
https://plugins.gradle.org/plugin/jmfayard.github.io.gradle-kotlin-dsl-libs
Issue Analytics
- State:
- Created 5 years ago
- Comments:9
Top Results From Across the Web
Plugin query - Contact with Id = xxx-xxxx does not exist
Hi,. I have replaced the OOTB address1_country field with a custom lookup list. I created an entity called Country, and created records of ......
Read more >What the difference in applying gradle plugin - Stack Overflow
The plugins block is the newer method of applying plugins, and they must be available in the Gradle plugin repository. The apply approach...
Read more >Allow application of the Android Gradle plugins ... - Issue Tracker
To apply the Android Gradle plugin one has to do the following: ... Given that the Android Gradle plugins are not published to...
Read more >Updating plugin throws " Cannot create more than one button ...
Updating plugin throws " Cannot create more than one button with id 'xxx' in toolbar with id 'xxx' in plugin with id 'cloud_xxx'...
Read more >Is it possible to test settings-plugins via 'testkit' in same repo?
I'm trying to test a settings-based plugin via “functional tests” ... an error An exception occurred applying plugin request [id: 'xxx'] …
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yes!
Ouch, that’s too bad about Google not publishing to plugins.gradle.org! Thanks for confirming. Can we consider this issue to be resolved?