quarkusio/quarkus · critical · RuntimeException

Failed to initialize Quarkus Maven context

Error message

Failed to initialize Quarkus Maven context

What it means

createMavenContext builds a QuarkusMavenContext (workspace model, remote repositories, etc.); any BootstrapMavenException during that process is wrapped in RuntimeException('Failed to initialize Quarkus Maven context'). It means Quarkus tooling could not construct its view of the Maven project/workspace — usually bad settings, an unresolvable parent POM, or an invalid project model. It is called by getMavenContext and createArtifactResolver, so it surfaces whenever Quarkus Maven plugin goals start up.

Source

Thrown at devtools/maven/src/main/java/io/quarkus/maven/components/QuarkusWorkspaceProvider.java:109

                            builder -> builder.addBeanInstance(versionResolver)
                                    .addBeanInstance(versionRangeResolver)
                                    .addBeanInstance(artifactResolver)
                                    .addBeanInstance(metadataResolver)
                                    .addBeanInstance(deployer)
                                    .addBeanInstance(remoteRepoManager)
                                    .addBeanInstance(settingsDecrypter)
                                    .addBean(ModelBuilder.class)
                                    .setSupplier(new BeanSupplier<ModelBuilder>() {
                                        @Override
                                        public ModelBuilder get(Scope scope) {
                                            return new MavenModelBuilder(ctx);
                                        }
                                    }).setPriority(100).build(),
                            DependencyFilter.ACCEPT);
                }
            };
        } catch (BootstrapMavenException e) {
            throw new RuntimeException("Failed to initialize Quarkus Maven context", e);
        }
    }

    public MavenArtifactResolver createArtifactResolver(BootstrapMavenContextConfig<?> config) {
        try {
            return new MavenArtifactResolver(createMavenContext(config));
        } catch (BootstrapMavenException e) {
            throw new RuntimeException("Failed to initialize Maven artifact resolver", e);
        }
    }
}

View on GitHub (pinned to e1c734241f)

Solutions

1. Run `mvn validate` first — fix any reported POM problems (missing parent, invalid XML, wrong coordinates).
2. Check ~/.m2/settings.xml validity and connectivity to repositories (proxy/mirror config); retry after network is restored.
3. Verify you are running the goal from a valid Maven project directory containing a buildable pom.xml.
4. Run with mvn -e -X to see the wrapped BootstrapMavenException cause and address it specifically (e.g. delete corrupt ~/.m2/repository metadata for the failing artifact).

Example fix

// before: running tooling in a directory without a resolvable parent
<parent><groupId>com.acme</groupId><artifactId>parent</artifactId><version>1.0</version></parent> // not in any repo
// after: install the parent first or fix its coordinates
cd ../parent && mvn install -N && cd ../app && mvn quarkus:add-extension -Dextensions="rest"

// validate the project model before bootstrapping Quarkus tooling
Process mvn = new ProcessBuilder("mvn", "-q", "validate")
        .directory(projectDir)
        .inheritIO()
        .start();
if (mvn.waitFor() != 0) {
    throw new IllegalStateException("Project model invalid; fix pom.xml/parent before running Quarkus goals");
}

try {
    MavenArtifactResolver r = workspaceProvider.createArtifactResolver(cfg);
} catch (RuntimeException e) {
    if (e.getMessage() != null && e.getMessage().contains("Failed to initialize Quarkus Maven context")) {
        throw new IllegalStateException("Maven context bootstrap failed: " + e.getCause(), e);
    }
    throw e;
}

When it happens

Trigger: Calling createMavenContext(config) (directly or via getMavenContext()/createArtifactResolver) when the bootstrap fails: invalid or unreachable settings.xml, unresolvable parent POM or BOM in the reactor, corrupt local repository metadata, or an invalid BootstrapMavenContextConfig (bad paths, wrong root project).

Common situations: Project with a missing or unbuildable parent POM; network/proxy preventing resolution of the parent/BOM during workspace bootstrap; settings.xml with a broken localRepository or profiles; running quarkus:add-extension / quarkus:dev in a directory that is not a valid Maven project root.

Related errors

• Failed to create application model resolver for
• The application module hasn't been built yet
• Unable to determine groupId and artifactId of the extension
• Local dependency <module> does not appear to have any source
• Hot reloadable dependency <moduleId> has not been compiled y

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