is it possible to set kotlin options in a gradle Plugin<Project>

# gradle

[rkeazor]

is it possible to set kotlin options in a gradle Plugin<Project>

[octylFractal]

assuming you can make sure the kotlin plugin is applied, yes, you can do anything you can do in a normal project

[octylFractal]

only difference is that there's no precompiled extensions, so you'll have to reference the types of those extensions, e.g. if you're working in kotlin, configure<KotlinJvmProjectExtension>

[rkeazor]

Thank you for the response @octylFractal

[rkeazor]

im trying to disable warnings regarding experimentalCoroutinesAPI in a plugin

[rkeazor]

open class ExperimentalExtension seems like it can be overriden to do this

[octylFractal]

don't think you should override anything

[octylFractal]

e.g. I would do

the<KotlinJvmProjectExtension>().target.compilations.forEach {
    it.kotlinOptions {
        jvmTarget = "1.8"
        freeCompilerArgs = freeCompilerArgs + listOf("-Xopt-in=kotlin.RequiresOptIn")
    }
}

but that's just my preferred style, you can use configure<KotlinJvmProjectExtension> with nested blocks as well

[rkeazor]

ohh nice one . Thanks for that

[rkeazor]

thats exactly what i was looking for

[gildor]

If you use Precompiled Script Plugins you will get type safe accessors and it would be a lot easier to use Gradle APIs, it will work exactly like in build.gradle.kts

[rkeazor]

@octylFractal I dont seem to have access to compilations. . target is a instance of Project correct ?

[rkeazor]

@gildor so Im trying to apply the logic to a existing plugin. so many modules can inherit from it.

[octylFractal]

I'm confused by what you mean

[octylFractal]

I explicitly said the<KotlinJvmProjectExtension>().target, which should make the type self-evident (look at the fields of KotlinJvmProjectExtension)

[octylFractal]

it's not a variable you need to supply in any way though, so it realistically shouldn't matter

[rkeazor]

Untitled

[octylFractal]

it's plural

[octylFractal]

also, that wont compile in any fashion, not sure if that's just pseudo code

[octylFractal]

all plugin actions typically happen in apply

[rkeazor]

yea its pseudo , its encapsulated in the apply(target: Project) function

[rkeazor]

but yea target.compilations doesn't seem to exsits

[octylFractal]

no idea, it's def. a field on any KotlinTarget

[octylFractal]

I would double check that target refers to the this.target there, and not your target: Project

[rkeazor]

O wait, yea Im dumb. Completely missed that 😅 . yea your right , it was ref the wrong target

[rkeazor]

my bad thanks

[rkeazor]

hey got one more question, have any of run into issues with artifactory , with gradle 6.3 and above?

[rkeazor]

particularly with it not being able to handle custom protocols like artifactory://

[octylFractal]

I don't recall if my artifactory-deployed projects use 6.3+

[rkeazor]

Yea keep running into this issue. funny enough if I build the project with gradlew it builds. but I can't sync the project in android studio

[rkeazor]

it might just be a ide issue not a gradle . since it resolves via gradlew