Skip to content
Latchkey

Maven "No plugin found for prefix" - Fix Goal Resolution

Maven could not map the goal prefix you typed to any plugin. Either the prefix is wrong, or the plugin lives in a group Maven does not search by default.

What this error means

A command like mvn spring-boot:run or mvn foo:bar fails before doing any work with No plugin found for prefix ..., listing the plugin groups Maven searched.

mvn output
[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

Common causes

Plugin group not registered

Maven only auto-searches org.apache.maven.plugins and org.codehaus.mojo for prefixes. A plugin in another group (e.g. org.springframework.boot) is invisible by prefix unless its group is registered.

Wrong or misremembered prefix

The goal prefix is not the artifactId - a typo or a non-existent prefix simply does not map to any plugin.

How to fix it

Register the plugin group

Add the plugin’s groupId to pluginGroups in settings.xml so the prefix resolves.

~/.m2/settings.xml
<settings>
  <pluginGroups>
    <pluginGroup>org.springframework.boot</pluginGroup>
  </pluginGroups>
</settings>

Invoke the plugin by full coordinates

Skip prefix resolution entirely by naming the plugin in full.

Terminal
mvn org.springframework.boot:spring-boot-maven-plugin:run

How to prevent it

  • Bind plugins to lifecycle phases in the POM so CI runs mvn package, not bare prefixes.
  • Register non-default plugin groups in settings.xml for the runner.
  • Document the exact Maven commands a pipeline expects.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →