Skip to content

Commit fb26ad6

Browse files
authored
Invert withTracing log output (#1295)
It seems that the booleans are inverted here for `printOnSuccess` as the compilation output is quite verbose for KSP and KAPT compilations. This logic also seems to mirror how tracing is intended to print in the rest of the codebase.
1 parent b563b57 commit fb26ad6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/main/kotlin/io/bazel/kotlin/builder/tasks/jvm/CompilationTask.kt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@ private fun JvmCompilationTask.runKaptPlugin(
278278
context.executeCompilerTask(
279279
args,
280280
compiler::compile,
281-
printOnSuccess = context.whenTracing { false } ?: true,
281+
printOnSuccess = context.whenTracing { true } ?: false,
282282
)
283283
}.let { outputLines ->
284284
// if tracing is enabled the output should be formatted in a special way, if we aren't
@@ -315,7 +315,7 @@ private fun JvmCompilationTask.runKspPlugin(
315315
context.executeCompilerTask(
316316
args,
317317
compiler::compile,
318-
printOnSuccess = context.whenTracing { false } ?: true,
318+
printOnSuccess = context.whenTracing { true } ?: false,
319319
)
320320
}.let { outputLines ->
321321
// if tracing is enabled the output should be formatted in a special way, if we aren't

0 commit comments

Comments
 (0)