https://gradle.com/ logo
Join Slack
Powered by
# plugin-development
  • s
    This message was deleted.
    t
    d
    +2
    • 5
    • 12
  • s
    This message was deleted.
    v
    r
    • 3
    • 5
  • s
    This message was deleted.
    r
    v
    m
    • 4
    • 12
  • s
    This message was deleted.
    b
    v
    +2
    • 5
    • 6
  • s
    This message was deleted.
    👍 1
    v
    ł
    • 3
    • 6
  • s
    This message was deleted.
    m
    a
    • 3
    • 29
  • s
    This message was deleted.
    m
    p
    • 3
    • 4
  • s
    This message was deleted.
    j
    e
    +6
    • 9
    • 70
  • s
    This message was deleted.
    r
    m
    +3
    • 6
    • 19
  • s
    This message was deleted.
    👀 1
    v
    a
    • 3
    • 3
  • s
    This message was deleted.
    v
    j
    • 3
    • 2
  • s
    This message was deleted.
    v
    b
    • 3
    • 12
  • a
    I'm using TestKit to test my Gradle plugin. I want to check that it doesn't log to lifecycle during project configuration. The very first time I run my test with args 
    clean --no-configuration-cache --no-build-cache
    , I can see in the log output:
    Copy code
    > Configure project :
> Configure project :subproject-goodbye
> Configure project :subproject-hello
> Task :clean
> Task :subproject-goodbye:clean
> Task :subproject-hello:clean
    So I can check the 
    BuildResult.output
    to verify that it contains this string exactly. But if I re-run the the second time, the test fails because it's missing the 
    Configure project
    lines. I've tried deleting the test project's 
    .gradle
    directory, but it didn't have any effect. Is there a nice flag I can use to force Gradle to configure all projects?
  • s
    This message was deleted.
    j
    e
    • 3
    • 4
  • s
    This message was deleted.
    m
    d
    • 3
    • 6
  • s
    This message was deleted.
    v
    t
    e
    • 4
    • 3
  • s
    This message was deleted.
    p
    v
    +2
    • 5
    • 11
  • s
    This message was deleted.
    👀 3
    ➕ 2
    v
    v
    +2
    • 5
    • 12
  • s
    This message was deleted.
    t
    m
    +2
    • 5
    • 17
  • s
    This message was deleted.
    r
    o
    v
    • 4
    • 9
  • s
    This message was deleted.
    e
    b
    +2
    • 5
    • 16
  • s
    This message was deleted.
    e
    r
    • 3
    • 4
  • s
    This message was deleted.
    ✅ 1
    d
    j
    • 3
    • 7
  • t
    I have a few questions regarding 
    ProjectBuild
    and usages in the unit tests: • it could be used just to check configuration state with some provided modifications to the 
    Project
    instance? Limitations are that it is not possible to use different Gradle versions with it, it does not run tasks execution and does not download any project dependencies - am I correct or there are more? • Is there any downsides to call 
    (Project as ProjectInternal).evaluate()
    ? (beside obvious that it is internal Gradle api)
  • s
    This message was deleted.
    ✅ 1
    j
    h
    +2
    • 5
    • 6
  • s
    This message was deleted.
    v
    r
    g
    • 4
    • 11
  • s
    This message was deleted.
    a
    t
    v
    • 4
    • 32
  • s
    This message was deleted.
    👀 1
    j
    • 2
    • 15
  • s
    This message was deleted.
    a
    • 2
    • 1
  • a
    can I configure the Kotlin DSL plugin to generate pre-compiled script plugins from a non-main source set? I would like to generate some test-plugins using the java-test-fixtures plugin. I think it’s possible using the 
    PrecompiledScriptPluginsSupport
    service: https://github.com/gradle/gradle/blob/34453d3231c84f0713123cde78536cb29d735281/subprojects/kotlin-dsl-plugins/src/main/kotlin/org/gradle/kotlin/dsl/plugins/precompiled/PrecompiledScriptPlugins.kt#L44-L50 I’ve made some progress, and IntelliJ seems to be happy, but I get an error when I try and build:
    Copy code
    > Task :compileTestFixturesKotlin FAILED
...
No script runtime was found in the classpath: class 'kotlin.script.templates.standard.ScriptTemplateWithArgs' not found. Please add kotlin-script-runtime.jar to the module dependencies
    Of course I could add the dependency directly, but I’d prefer to match the way that Gradle is doing it. However, I can’t find out what’s missing (code in thread). Any clues how Gradle normally adds the script-runtime dependency?
1...101112...36Latest