• m

    mingkangpan

    5 years ago
    anyone using Android Studio 3.0 Beta2? and facing error with 'kotlin-kapt' and dagger2? everytime if I change the dagger tree I have to clean the project or project wont compile where do I report a bug for kapt actually? 😄
    m
    1 replies
    Copy to Clipboard
  • j

    janusz

    5 years ago
    I’ve tried
    detekt
    and
    ktlint
    . Do you know if there is anything else?
    j
    t
    2 replies
    Copy to Clipboard
  • t

    trevjones

    5 years ago
    assuming they are just data classes and don’t house any logic it would be best to ignore them in both your testing efforts as well as your coverage report.
    t
    t
    +1
    5 replies
    Copy to Clipboard
  • e

    Eugenio

    5 years ago
    message has been deleted
    e
    1 replies
    Copy to Clipboard
  • trubesv

    trubesv

    5 years ago
    Hello all 🙂 Is there a way to "speed up" editing
    .gradle
    files in IntelliJ? It gets stuck for a few second when I type each character, like it's saving/reloading.. Very frustrating Also, Gradle eats up my RAM incrementally, I think I messed my setup 😕 Do you have any advice regarding these issues? Thanks! :kotlin:
    trubesv
    gaetan
    4 replies
    Copy to Clipboard
  • a

    artem_zin

    4 years ago
    JB people, can you please explain performance differences between running Gradle build with separate Kotlin Compiler Daemon vs in-process compilation? What is the lifecycle of in-process compilation? Isn’t Gradle daemon enough to keep compiler “hot” (class loading, JIT)? Thanks! --- Reason why I’m asking is because we’re facing issues with Kotlin Compiler Daemon with a single Kotlin module in project when we build it with
    --parallel
    , see
    <https://youtrack.jetbrains.com/issue/KT-15562#comment=27-2494744>
    a
    gildor
    +2
    28 replies
    Copy to Clipboard
  • b

    bringoff

    4 years ago
    I’m facing random compiling error on CI. The same code may compile successfully and after adding git tag (which triggering new CI check) the same code fails to build with error
    Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
    . I’ve tried to add different params to build command, but this didn’t help. Adding
    -Dkotlin.compiler.execution.strategy=in-process
    broke android data binding annotation processing. My current gradle build command looks like this:
    ./gradlew -Pkotlin.incremental=false -Dorg.gradle.parallel=false -Dorg.gradle.daemon=false testBetaQaUnitTest lintBetaQa testProdReleaseUnitTest lintProdRelease
    b
    a
    3 replies
    Copy to Clipboard
  • h

    holgerbrandl

    4 years ago
    h
    ilya.gorbunov
    +1
    10 replies
    Copy to Clipboard
  • a

    artem_zin

    4 years ago
    Between Kotlin 1.1.51 and 1.1.60
    kotlin-annotation-processing
    artifact was discontinued and now there is a
    kotlin-annotation-processing-gradle
    instead (as well as
    -maven
    which was there for some time)
    <https://github.com/JetBrains/kotlin/commit/feee93186bdab504c5bf94d1c046bf7f2a0697af>
    1. Does it mean that
    -gradle
    version will become more Gradle-specific? Reason why I'm asking is because OkBuck + Buck need it to support Kapt and relied on
    kotlin-annotation-processing
    before, but now it's gone 2. Changelog doesn't seem to reflect this change
    <https://github.com/JetBrains/kotlin/blob/1.1.60/ChangeLog.md>
    cc @h0tk3y
    a
    y
    +1
    4 replies
    Copy to Clipboard
  • kirillrakhman

    kirillrakhman

    4 years ago
    the 30 seconds should only be spent on the first build. incremental build should only rebuild the files you changed
    kirillrakhman
    m
    +1
    6 replies
    Copy to Clipboard