No plugin found for prefix 'sonar' in the current project Error while analysis

Hello Team,

The Azure Devops pipeline we set up to perform the Sonar analysis is failing with the error shown below. This issue started occurring today. Could you please help us with this urgently, as all quality checks are currently failing?

[ERROR\] No plugin found for prefix 'sonar' in the current project and in the plugin groups \[org.apache.maven.plugins, org.codehaus.mojo\] available from the repositories \[local (C:\\Users\\VssAdministrator\\.m2\\repository), central ( https://repo.maven.apache.org/maven2 )\] -> \[Help 1\]
2025-11-24T17:16:00.3921424Z org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'sonar' in the current project and in the plugin groups \[org.apache.maven.plugins, org.codehaus.mojo\] available from the repositories \[local (C:\\Users\\VssAdministrator\\.m2\\repository), central ( https://repo.maven.apache.org/maven2 )\]
2025-11-24T17:16:00.3923322Z     at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:90)
2025-11-24T17:16:00.3924285Z     at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:247)
2025-11-24T17:16:00.3936075Z     at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:209)
2025-11-24T17:16:00.3936817Z     at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:94)
2025-11-24T17:16:00.3937528Z     at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:76)
2025-11-24T17:16:00.3938175Z     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:84)
2025-11-24T17:16:00.3938690Z     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
2025-11-24T17:16:00.3939176Z     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
2025-11-24T17:16:00.3940214Z     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
2025-11-24T17:16:00.3940714Z     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
2025-11-24T17:16:00.3941182Z     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
2025-11-24T17:16:00.3941646Z     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
2025-11-24T17:16:00.3942100Z     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
2025-11-24T17:16:00.3942612Z     at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77)
2025-11-24T17:16:00.3943169Z     at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
2025-11-24T17:16:00.3943698Z     at java.lang.reflect.Method.invoke (Method.java:569)
2025-11-24T17:16:00.3944181Z     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255)
2025-11-24T17:16:00.3944703Z     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201)
2025-11-24T17:16:00.3945280Z     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361)
2025-11-24T17:16:00.3945824Z     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314)
2025-11-24T17:16:00.3946231Z \[ERROR\] 
2025-11-24T17:16:00.3946533Z \[ERROR\] 
2025-11-24T17:16:00.3946934Z \[ERROR\] For more information about the errors and possible solutions, please read the following articles:
2025-11-24T17:16:00.3947436Z \[ERROR\] \[Help 1\] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
2025-11-24T17:16:00.3948038Z \[DEBUG\] Shutting down adapter factory; available factories \[file-lock, rwlock-local, semaphore-local, noop\]; available name mappers \[discriminating, file-gav, file-hgav, file-static, gav, static\]

Kind Regards,

Renjini.

Hi Renjini,

This hit some of our old projects too. :sweat_smile:

Take a look at the fix here:

 
HTH,
Ann

Hi Ann,

Thank you for your quick response. I have upgraded both the SonarCloudPrepare (SonarCloudPrepare@3) and SonarCloudPublish (SonarCloudPublish@3) tasks in my pipeline, and that has resolved the issue.

Kind Regards,

Renjini

1 Like