quarkusio/quarkus · error · MojoExecutionException
Failed to initialize Quarkus Maven extension manager
Error message
Failed to initialize Quarkus Maven extension manager
What it means
The Quarkus Maven plugin initializes the Quarkus project model (MavenProjectBuildFile) which may need to resolve the extension registry. When registry resolution fails with a RegistryResolutionException, the plugin wraps it in this MojoExecutionException, meaning the Quarkus extension manager could not be initialized.
Source
Thrown at devtools/maven/src/main/java/io/quarkus/maven/QuarkusProjectMojoBase.java:106
// Validate Mojo parameters
validateParameters();
final Path projectDirPath = baseDir();
BuildTool buildTool = QuarkusProject.resolveExistingProjectBuildTool(projectDirPath);
if (buildTool == null) {
// it's not Gradle and the pom.xml not found, so we assume there is no project at all
buildTool = BuildTool.MAVEN;
}
final QuarkusProject quarkusProject;
if (BuildTool.MAVEN.equals(buildTool) && project.getFile() != null && bomVersion == null) {
try {
quarkusProject = MavenProjectBuildFile.getProject(projectArtifact(), project.getOriginalModel(), baseDir(),
project.getModel().getProperties(), artifactResolver(), getExtensionCatalogResolver(),
getMessageWriter(),
null);
} catch (RegistryResolutionException e) {
throw new MojoExecutionException("Failed to initialize Quarkus Maven extension manager", e);
}
} else {
final ExtensionCatalog extensionCatalog = resolveExtensionCatalog();
final List<ResourceLoader> codestartsResourceLoader = CodestartResourceLoadersBuilder
.codestartLoadersBuilder(log)
.artifactResolver(artifactResolver())
.catalog(extensionCatalog)
.build();
quarkusProject = QuarkusProject.of(baseDir(), extensionCatalog,
codestartsResourceLoader, log, buildTool,
MavenProjectBuildFile.resolveJavaVersion(project.getModel().getProperties()));
}
doExecute(quarkusProject, getMessageWriter());
}
protected MessageWriter getMessageWriter() {
return log == null ? log = new MojoMessageWriter(getLog()) : log;View on GitHub (pinned to e1c734241f)
Solutions
- Check network connectivity / proxy settings so the Quarkus registry (registry.quarkus.io) is reachable
- Review registry configuration (quarkus.registry endpoints in .quarkus/config.yaml) for typos or invalid URLs
- Refresh or delete the stale local registry cache (~/.quarkus) and retry
- Inspect the underlying RegistryResolutionException (cause) for the exact host/reason that failed
Defensive patterns
Strategy: try-catch
Validate before calling
// pre-check registry reachability before running the goal
try (var s = new Socket()) {
s.connect(new InetSocketAddress("registry.quarkus.io", 443), 5000);
} catch (IOException e) {
System.err.println("Quarkus registry unreachable; check network/proxy before running");
} Try / catch
try {
mojo.execute();
} catch (MojoExecutionException e) {
if (e.getMessage().equals("Failed to initialize Quarkus Maven extension manager") && e.getCause() instanceof RegistryResolutionException) {
// check network/proxy and registry config, clear ~/.quarkus cache, retry
} else {
throw e;
}
} Prevention
- Ensure registry.quarkus.io is reachable from CI and dev environments (proxy/VPN settings)
- Keep quarkus.registry configuration valid in .quarkus/config.yaml
- Refresh or clear the local registry cache when upgrading Quarkus versions
When it happens
Trigger: Executing a Quarkus MoJo (execute in QuarkusProjectMojoBase) where MavenProjectBuildFile.getProject requires resolving remote Quarkus registries and the resolution fails (network error, unreachable/bad registry URL, corrupt local registry cache).
Common situations: No network access or behind a proxy blocking registry.quarkus.io; misconfigured quarkus.registry entries in .quarkus/config.yaml or Maven settings; a registry URL pointing to a non-existent host; corrupted local registry cache in ~/.quarkus.
Related errors
- Failed to resolve the recommended Quarkus extension catalog
- Failed to resolve Quarkus extension catalog
- Failed to resolve the extension catalog for stream '${stream
- Failed to resolve application model <appArtifact> dependenci
- Failed to resolve the available updates
AI-assisted analysis of quarkusio/quarkus@e1c734241f (2026-09-05).
Data as JSON: /api/errors/56801eea65927bf3.
Report an issue: GitHub.