You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As currently written in the example code for gradle, It is the legacy way to set up plugins.
If we were to change to code that uses the plugins block, it would be a bit more user-friendly,
nd it would be a simple change to make by reducing the number of lines in the code example.
Thanks for the suggestion. Until the plugin is published to Gradle's plugin portal (#309), this change as proposed will break people's builds as they won't be able to resolve the plugin. It could be addressed by also configuring the plugin repositories in settings.gradle to add mavenCentral(). I'm not totally convinced it's worth it though. WDYT, @philwebb?
Given that the project is mainly for ourselves, I don't think we should make the change. We can add a note to #309 to update the docs if we get publishing working.
As currently written in the example code for gradle, It is the legacy way to set up plugins.
If we were to change to code that uses the plugins block, it would be a bit more user-friendly,
nd it would be a simple change to make by reducing the number of lines in the code example.
AS-IS
TO-BE
The text was updated successfully, but these errors were encountered: