quarkusio/quarkus · error · MojoExecutionException
Failed to list extensions
Error message
Failed to list extensions
What it means
ListExtensionsMojo (`mvn quarkus:list-extensions`) lists extensions available in the configured registry for the project's platform. Any exception while fetching/rendering that list is wrapped in this MojoExecutionException.
Source
Thrown at devtools/maven/src/main/java/io/quarkus/maven/ListExtensionsMojo.java:79
.search(searchPattern)
.category(category)
.installed(installed);
listExtensions.execute();
if (DEFAULT_FORMAT.equalsIgnoreCase(format)) {
log.info("");
log.info(ListExtensions.MORE_INFO_HINT, "-Dformat=full");
}
if (!installed && (category == null || category.isBlank())) {
log.info("");
log.info(ListExtensions.FILTER_HINT, "-Dcategory=\"categoryId\"");
}
log.info("");
log.info(ListExtensions.ADD_EXTENSION_HINT,
"pom.xml", "./mvnw quarkus:add-extension -Dextensions=\"artifactId\"");
} catch (Exception e) {
throw new MojoExecutionException("Failed to list extensions", e);
}
}
}
View on GitHub (pinned to e1c734241f)
Solutions
- Confirm the platform BOM version exists and matches the plugin version
- Check network/proxy access to the registry
- Run with -e and read the cause chain for the failing artifact/URL
- Refresh metadata with -U
- Align quarkus.platform.version and quarkus-maven-plugin versions
Example fix
// before <quarkus-maven-plugin.version>2.16.0</quarkus-maven-plugin.version> with platform 3.x // after <quarkus-maven-plugin.version>3.2.9.Final</quarkus-maven-plugin.version> matching platform 3.2.9.Final
Defensive patterns
Strategy: try-catch
Validate before calling
// align versions before invoking mvn help:evaluate -Dexpression=quarkus.platform.version -q -DforceStdout mvn help:evaluate -Dexpression=quarkus-maven-plugin.version -q -DforceStdout // both must match
Try / catch
try {
// mvn quarkus:list-extensions
} catch (MojoExecutionException e) {
log.error("Extension listing failed: " + e.getCause().getMessage());
} Prevention
- Keep plugin and platform versions identical
- Use quarkus:update to align versions
- Verify network access before offline CI stages
When it happens
Trigger: Running `mvn quarkus:list-extensions` when registry lookup fails, the platform BOM is unresolvable, or application model resolution throws.
Common situations: Platform version pinned to an unpublished release; offline build machine; registry returning HTTP errors; version mismatch between quarkus-maven-plugin and platform BOM.
Related errors
- Unable to add extensions
- Failed to resolve Quarkus extension catalog
- The project was created but (some of) the requested extensio
- Failed to resolve the extension catalog for stream '${stream
- Failed to resolve the available updates
AI-assisted analysis of quarkusio/quarkus@e1c734241f (2026-09-05).
Data as JSON: /api/errors/8d4da8c144e31a39.
Report an issue: GitHub.