The settings itself is for Kotlin arguments, and you are trying to pass javac arguments there, so may be you need to configure javac instead?

allprojects {
  gradle.projectsEvaluated {
    tasks.withType(JavaCompile) {
        options.compilerArgs << "-Xmaxerrs" << "1000"
    }
  }
}

E.g. like this

I was using that

but it stopped working after kotlin 1.1

So I guess that the problem was on the arguments not being copied to the Kapt task compiler

But apparently it is something else

hmm, may be it’s on kapt side now? May be @yan can help…

The issue I linked above, was resolving that arguments copy to kapt

it is accompanied by a test as well

although it only checks Boolean args

Could you please add these details to the issue? About maxerrs, what you’ve been using before, and how it broke with 1.1 Any detail can matter.

Yeap, I did

Ah, yep, I see, thanks!

Added some more

@pavlospt KT-15994 is about the new kapt implementation (which is enabled by

apply plugin: 'kotlin-kapt'

). In the issue compiler arguments were not copied from

compileKotlin

task to

compileKapt

task. The new implementation does not use javac, so I'm afraid it does not support

-Xmaxerrs

(you can add a feature request at https://youtrack.jetbrains.com/issues/KT). The old implementation (

kotlin-kapt

plugin is not applied) is expected to work as it was in 1.0.x. // cc @yan

Is there any way to enable it with the current implementation?

Or is a new feature request mandatory?

@pavlospt what do you mean by the current implementation? Let's stick with the following definitions: 1. Old kapt (aka kapt1) does not require explicit enabling. 2. New kapt (aka kapt3) is enabled by applying the plugin

kotlin-kapt

. kapt1 is expected to support

-Xmaxerrs

because it is run via javac. kapt3 is not expected to support

-Xmaxerrs

. I also not sure if it is needed, because AFAIK Kotlin compiler does not have a limit for a number of compile errors. Am I right that your issue is not related to

1.0.x

->`1.1` switch (that would be a regression), but rather it is related to

kapt1

->`kapt3` switch?

Not quite sure, the thing is that we used to get all of the code generation errors displayed.

Right now if something happens during the generation of code from an Annotation we get back no errors. Even more, the message says “Check log for more details”. I couldn’t find out what the log is, even by searching the source code of the plugin

So apparently there is no way for us to understand what has gone wrong

@pavlospt does it happen in AS/Intellij or in the console too?

Happens in console as well!

—debug —info —stacktrace do not provide any meaningful insight

@pavlospt Looks like errors are not passed from the Kotlin daemon to the Gradle process. Can you reproduce this behavior with some project you could share?

Due to the complexity of it, I can not recreate it.

We use Dagger Databinding and StorIO which all have code generation.

@yan ☝️ (kind ping in case you did not see my answer, ignore otherwise)

@pavlospt Then can you please create an issue and describe you case with providing some more information? At least

build.gradle

file is appreciated. I will try to reproduce this.

You need the root and the main module

build.gradle

files ?