What This Error Means
Maven cannot map that plugin prefix to a real plugin artifact, usually because the plugin is undeclared or missing from configured plugin repositories.
How to Fix It
Try running the goal using full coordinates:mvn groupId:artifactId:version:goal (this bypasses prefix mapping).
Preferably, add the plugin to your pom.xml under <build><plugins> (and set the plugin version explicitly).
If the plugin is hosted outside Maven Central, configure the correct <pluginRepositories> (or a mirror in settings.xml).
If you use a corporate mirror/repository manager, confirm it proxies plugin repositories and that the plugin is not blocked by policy.
Retry the command, and if needed, run with debug logs:mvn -X <prefix>:<goal>
Why It Happens
The plugin is not declared in the project and Maven cannot resolve it by prefix from configured plugin groups.
The plugin repository is not configured (or is blocked by proxy/auth/TLS issues).
You are offline or using a mirror that does not proxy the plugin's upstream repository.
How to Verify
Re-run the original <prefix>:<goal> command and confirm Maven resolves and runs the plugin.
Confirm the plugin artifact exists under ~/.m2/repository/.
Manual plugin resolution checks
Confirm you can reach Maven Central (or your mirror) from this machine by resolving any known plugin:mvn -q -DskipTests help:effective-pom
Search your pom.xml for a plugin declaration that matches the goal you're trying to run under <build><plugins>.
If the plugin is not in Central, confirm you have a <pluginRepositories> entry (or a mirror) that contains it.
Examples
[ERROR] No plugin found for prefix 'spring-boot' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (~/.m2/repository), central (https://repo.maven.apache.org/maven2)]How plugin prefix resolution works
When you run mvn <prefix>:<goal>, Maven must resolve the prefix to a plugin artifact (groupId:artifactId).
Maven searches known plugin groups and repositories for plugin metadata that declares that prefix.
If Maven cannot find the plugin in any configured plugin repositories, prefix resolution fails.
Prevention Tips
Declare build plugins in pom.xml and pin plugin versions (avoid relying on prefix auto-discovery).
Use a repository manager mirror that includes plugin repositories and caches them for CI stability.
Keep settings.xml consistent across environments so plugin resolution does not vary by machine.
Where This Can Be Triggered
github.com/apache/maven/blob/maven-3.9.11/maven-core/src/main/java/org/apache/maven/plugin/prefix/internal/DefaultPluginPrefixResolver.java
Maven throws NoPluginFoundForPrefixException when it cannot resolve a plugin prefix from available plugin groups/repositories. - GitHub
if (requests.isEmpty()) {
continue;
}
throw new NoPluginFoundForPrefixException(prefix, session, pluginGroups, requests);