you need to refer to extension classes convention classes mo

Question

you need to refer to extension classes convention classes more explicitly in Kotlin DSL they don t magically appear as extension properties on the project

Florian Wiesner · Answer

do you know any good reference

araqnid · Answer

e g `the lt JavaPluginConvention gt sourceCompatibility = JavaVersion VERSION 1 8`

araqnid · Answer

a good reference no I had to figure this out by noodling around

Florian Wiesner · Answer

ok let me give it a try slightly smiling face

araqnid · Answer

there is a withConvention extension function intended to be used on any object that implements hasConvention e g source sets etc not just projects

araqnid · Answer

which I used like this ```val SourceSet scala SourceDirectorySet get = withConvention ScalaSourceSet class scala ```

Florian Wiesner · Answer

well I m working with extensions not conventions

araqnid · Answer

I got the impression they were mixed together

Florian Wiesner · Answer

conventions are the older concept

Florian Wiesner · Answer

and are replaced by extensions over tome

Florian Wiesner · Answer

time

Florian Wiesner · Answer

which is why I m implementing an extension

araqnid · Answer

the DSL plugin typically uses extension to mean Kotlin extension functions though

Czar · Answer

Just use `plugins ` block instead of `buildscript ` that will generate proper DSL for you e g ```plugins java java sourceCompatibility = VERSION 1 8 targetCompatibility = VERSION 1 8 ```

Florian Wiesner · Answer

ha seems there is a problem with the test runner

araqnid · Answer

there is an `ExtensionContainerExtensions kt` in the DSL plugin to allow you to write `extensions xxx ` etc

araqnid · Answer

ah right so things like `reporting` are project extensions

Florian Wiesner · Answer

weird one ``` plugins id info florian wiesner magicdraw ```

Florian Wiesner · Answer

it is found

Florian Wiesner · Answer

but

Florian Wiesner · Answer

`the lt florianwiesner gradle magicdraw MagicDrawExtension gt ` leads to an unresolved reference

Florian Wiesner · Answer

will dig deeper thanks < araqnid>

araqnid · Answer

is your extension registered with a name if so as Alexander said it should have been added to the generated glue so you can just refer to it by name

araqnid · Answer

you can also just call `extensions findByType ReportingExtension class java ` which that should be sugar for

Florian Wiesner · Answer

well I have a plugin descriptor under META INF

Florian Wiesner · Answer

and I currently try gettings things work under Gradle s test kit

Florian Wiesner · Answer

using Spek as my test framework

Florian Wiesner · Answer

my dynamic test script uses the `plugins ` DSL

Florian Wiesner · Answer

and I see the plugin to get loaded

araqnid · Answer

don t you have to call something from the plugin method to register the project extension

Florian Wiesner · Answer

``` class MagicDrawGradlePlugin Plugin lt Project gt private lateinit var project Project override fun apply project Project if project == null throw GradleException project must not be null this project = project val extension = addExtension lt MagicDrawExtension gt magicdraw project objects val verifyMagicDrawTask = project tasks create verifyMagicDraw VerifyMagicDrawTask class java verifyMagicDrawTask installDir = extension installDir as String private inline fun lt reified T gt addExtension name String vararg args Any T = project extensions create name T class java args ```

Florian Wiesner · Answer

let me make a snippet

araqnid · Answer

right so it s registered as `magicdraw`

araqnid · Answer

so you should be able to write `magicdraw ` in the build script and the glue should have made a Project magicdraw extension property

Florian Wiesner · Answer

`magicdraw ` is there

Florian Wiesner · Answer

but the installDir property is not recognized

araqnid · Answer

that s a property of the task or the extension or both

Florian Wiesner · Answer

both

araqnid · Answer

are you running the test from IntelliJ or Gradle command line I had trouble running this kind of test from IntelliJ

Florian Wiesner · Answer

in the apply function I copy the property value over to the newly created task

araqnid · Answer

with it using old versions of the classes under test

Florian Wiesner · Answer

I run it from gradle

araqnid · Answer

you copy it from the project extension to the task at the time the plugin is applied that sounds a bit fishy

Florian Wiesner · Answer

I wonder whether the test framework `GradleRunner` supports Kotlin DSL

Florian Wiesner · Answer

this is just a trial so far

Florian Wiesner · Answer

and btw that s even done in the Gradle docs when a task is auto generated from the plugin

araqnid · Answer

I suspect that if it didn t you encounter problems much earlier

Florian Wiesner · Answer

and I see a big issue

araqnid · Answer

ah hmm I should really get more acquainted with those

Florian Wiesner · Answer

well how would you generate a default task definition without having the plugin code do so wink

araqnid · Answer

so what happens when the build file changes the settings in the extension object

Florian Wiesner · Answer

anyway `plugins id ` finds my plugin and loads it

Florian Wiesner · Answer

but the script cannot find my classes

Florian Wiesner · Answer

imports fail

Florian Wiesner · Answer

so I guess that the test runner only sees the proxies

Florian Wiesner · Answer

but not the plugin classes

Florian Wiesner · Answer

`plugins ` might work because it is somewhat separated from the rest of the script

Florian Wiesner · Answer

which is why ``` val fooVersion String by extra plugins id bar version fooVersion ``` won t work

araqnid · Answer

yes plugins has to be right at the top iirc

Florian Wiesner · Answer

from a Gradle script perspective yes

Florian Wiesner · Answer

it has to be the first element after `buildscript`

araqnid · Answer

well using plugins should replace buildscript entirely

Florian Wiesner · Answer

but Kotlin could of course to things ahead of the `plugins` block

Florian Wiesner · Answer

tell that to the JUnit platform guys

Florian Wiesner · Answer

I will investigate and update this thread

araqnid · Answer

kotlin dsl aiui must grab the set of plugins use that to generate the glue project class with all the extensions conventions in and then compile the script with an instance of the glue project as receiver

araqnid · Answer

you can see the glue class if you ctrl+click on sth like java or reporting in a build gradle kts

Florian Wiesner · Answer

guess that s option B on my keyboard

Florian Wiesner · Answer

but really I assume there is breakage in the test runner

araqnid · Answer

something like that

Florian Wiesner · Answer

I will test publish the plugin to MavenLocal

Florian Wiesner · Answer

and then have a standalone project use it

araqnid · Answer

I m trying it here but even explicitly requesting the extension I m creating by name isn t working so

Florian Wiesner · Answer

I have to leave for dinner Will look into it tomorrow and update the thread

Florian Wiesner · Answer

thanks so far

araqnid · Answer

hmph yes I can register a project extension and it seems to work when referenced entirely separately but not when trying to use GradleRunner

araqnid · Answer

the glue class is written to somewhere like ` tmp gradle test kit shaslam caches 4 5 gradle kotlin dsl accessors` i tried just removing the caches no change

araqnid · Answer

but that generated class doesn t specify the type of my project extension the extension property is type `Any`

araqnid · Answer

so it seems lined up with the problem you re seeing of not finding the classes in the build script

araqnid · Answer

it writes in a comment above the extension property that the named class is not available so it knows what the type should be it just couldn t load it

araqnid · Answer

``` Configures the webpack com timgroup gradle webpack WebpackProjectExtension project extension `webpack` is not accessible in a type safe way because `com timgroup gradle webpack WebpackProjectExtension` is not available fun Project `webpack` configure Any gt Unit Unit = extensions configure webpack configure ```

araqnid · Answer

but publishing to mavenLocal and pulling it into another project generates the glue class fine ツ

araqnid · Answer

same result with Gradle 4 6 There is also a < C19FD9681|gradle> btw wink

Florian Wiesner · Answer

ah thanks

mkobit · Answer

saw the post in < C19FD9681|gradle> this sounds similar to