quarkusio/quarkus · error · GradleException

WTF

Error message

WTF

What it means

A placeholder/debug message in QuarkusShowEffectiveConfig.dumpEffectiveConfiguration: the outer catch (Exception e) prints the stack trace and rethrows it as a GradleException with the literal message 'WTF'. It signals that some unexpected (non-IO) exception occurred while dumping the effective configuration — the real cause is in the cause chain and in the printed stack trace.

Source

Thrown at devtools/gradle/gradle-application-plugin/src/main/java/io/quarkus/gradle/tasks/QuarkusShowEffectiveConfig.java:104

                    fastJar,
                    runnerJar(),
                    nativeRunner(),
                    sourceNames.stream().collect(Collectors.joining("\n        ", "\n        ", "\n")));

            if (getSaveConfigProperties().get()) {
                Properties props = new Properties();
                props.putAll(effectiveConfig.getValues());
                Path file = buildDir.toPath().resolve(finalName + ".quarkus-build.properties");
                try (BufferedWriter writer = newBufferedWriter(file)) {
                    props.store(writer, format("Quarkus build properties with JAR type %s", jarType));
                } catch (IOException e) {
                    throw new GradleException("Failed to write Quarkus build configuration settings", e);
                }
                getLogger().lifecycle("\nWrote configuration settings to {}", file);
            }
        } catch (Exception e) {
            e.printStackTrace();
            throw new GradleException("WTF", e);
        }
    }
}

View on GitHub (pinned to e1c734241f)

Solutions

1. Read the printed stack trace (e.printStackTrace() output appears just above the 'WTF' exception) — the root cause is there.
2. Inspect the cause chain of the GradleException (gradle run with --stacktrace / --scan).
3. Fix the offending quarkus.* property identified in the stack trace.
4. If it's a plugin bug, report it with the stack trace — the 'WTF' message itself is a code smell that should carry a descriptive message.

try {
    ./gradlew quarkusShowEffectiveConfig
} catch (GradleException e) {
    if ("WTF".equals(e.getMessage())) {
        e.getCause().printStackTrace(); // real cause is in the cause chain and printed stack trace
    }
}

When it happens

Trigger: Any RuntimeException escaping the inner logic of dumpEffectiveConfiguration — e.g. NPE from effectiveConfig.getValues(), an InvalidConfigurationFormatException from the formatter, or an error resolving effectiveConfig — inside the try block guarded by the outer catch.

Common situations: Malformed or conflicting quarkus.* configuration properties that make the effective-config model resolution fail; a bug/regression in the Gradle plugin; running the task in a project where the Quarkus extension was not applied correctly.

Related errors

• Failed to write Quarkus build configuration settings
• Unable to read the resolved model from: ${resolvedModelPath}
• Failed to resolve ${appArtifact}
• Requested artifact ${appArtifact} does not match project ${g
• No platforms detected in the project

AI-assisted analysis of quarkusio/quarkus@e1c734241f (2026-09-05). Data as JSON: /api/errors/1b19d025957dcee2. Report an issue: GitHub.