also. I suppose this would work only for core plug...
# gradle
a
also. I suppose this would work only for core plugins where the plugin classes are already found in the classpath (hence the import statements seen at the top of t examples) but how would this mechanism work for 3rd party plugins? you may remember the
plugins
block introduced in Gradle 2.1, which delivers an unified approach to applying core and 3rd party plugins. I'm afarid such block can't be applied unless Kotlin scripts gain the same capabilities Groovy offers with `@Grab`for example