This message was deleted Gradle Community #community-support

Join Slack

This message was deleted.

# community-support

Slackbot

01/18/2023, 7:26 PM

This message was deleted.

Tyler Helmuth

01/18/2023, 7:34 PM

Was able to accomplish this using the following code in the script plugin

Copy code

interface ExtJSPluginExtension {
    Property<String> getAppDir()
}

def extension = project.extensions.create("extjs", ExtJSPluginExtension)

Jendrik Johannes

01/18/2023, 7:36 PM

Yes and you should! 🙂 This is the DSL Extension concept of Gradle. There are many things you can do there, but the most compact way is to create an Interface (using Java/Kotlin/Groovy) with

Property<..>

s and register it as an extension. I have a quite minimal example here: https://github.com/jjohannes/understanding-gradle/blob/main/07_Implementing_Tasks_[…]gic/java-plugins/src/main/kotlin/my-java-application.gradle.kts https://github.com/jjohannes/understanding-gradle/blob/main/07_Implementing_Tasks_[…]/java-plugins/src/main/kotlin/myproject/tasks/MyAppExtension.kt https://github.com/jjohannes/understanding-gradle/blob/main/07_Implementing_Tasks_and_Extensions/my-project/app/build.gradle.kts#L5-L7

party gradlephant 1

Tyler Helmuth

01/18/2023, 7:37 PM

Thanks 🙂 I'll check those examples

Jaron Couvreur

01/19/2023, 11:55 AM

Hi. Am I correct in stating that you can only use extension values inside blocks of lazy configuration? Otherwise the extension hasn't received its value yet, and you get this error:

Copy code

Cannot query the value of extension 'fooExtension' property 'foo' because it has no value available.

Jaron Couvreur

01/19/2023, 11:57 AM

for example like so:

Copy code

interface FooExtension {
    val foo: Property<String>
}

val fooExtension = extensions.create<FooExtension>("fooExtension")

tasks {
    // doesn't work
    println(fooExtension.foo.get())

    // works
    withType<Test>().configureEach {
        println(fooExtension.foo.get())
    }
}

Tyler Helmuth

01/19/2023, 5:08 PM

@Jaron Couvreur I just ran into this myself. I had to use project.afterEvaluate to get the extension values to configure my "jar" task, but it seems dirty. edit: Found out that because I am configuring the jar task with a closure, it creates and configures the task eagerly. By removing the closure and using tasks.named("jar") { I am able to pick up the extension values.

Jendrik Johannes

01/20/2023, 11:41 AM

Ideally, you won't have to call

get()

at all. Instead, you just pass the provider in the task configuration. Then

get()

is only called during task execution. That's the idea behind the provider/property concept - you only pass around references to values. This way, the order in which things are done during configuration no longer matters. Some Tasks in Gradle and plugins unfortunately do not support providers yet. 😕 Then what you describe is usually sufficient - use task configuration avoidance (

named()

forEach()

) so that

get()

is called late in the configuration phase. Still, I would be interested why you had to call

get()

for the Jar task. The API of the task is not perfect, but usually there is some way to use it without calling

get()

already. Mind to share an example?

👍 1

3 Views

Open in Slack

Previous Next