Sonar Maven Plugin 1.0-beta-2: What Changed and How to Configure Legacy Builds

Originally published on 2010-09-14; fully revised and updated.

This article explains a historical release of the Sonar Maven Plugin (1.0-beta-2) announced by the Mojo team. It is most useful for engineers maintaining older Maven/Sonar integrations who need to understand what changed in configuration behavior and how version compatibility affects execution.

Primary source: Sonar mojo 1.0-beta-2 release post.

What changed in 1.0-beta-2

Based on the original announcement, version 1.0-beta-2 focused on making configuration easier when working with repository managers such as Archiva or Nexus.

• With 1.0-beta-2, no additional settings were required for that repository-manager scenario.
• In 1.0-beta-1, teams needed to declare a mirror in Maven settings.
• This improvement required Sonar 2.2+.
• When used with Sonar 2.1 or older, the improvement was automatically disabled.
• The release note says upgrade behavior should be automatic when using mvn sonar:sonar.

Beta-1 vs beta-2 behavior at a glance

Legacy execution flow

flowchart TD
    A[Run mvn sonar:sonar] --> B[Resolve Sonar Maven Plugin]
    B --> C{Sonar server version}
    C -- 2.2 or newer --> D[Use beta-2 improvement]
    C -- 2.1 or older --> E[Improvement disabled]
    D --> F[Proceed with simplified setup]
    E --> G[Proceed with legacy behavior]

Commands and configuration examples

The source post includes one explicit execution shortcut. The snippets below are practical examples for maintaining older Maven environments.

Run Sonar analysis from Maven

mvn sonar:sonarCode language: CSS (css)

Legacy mirror declaration pattern (beta-1 style)

<settings>
  <mirrors>
    <mirror>
      <id>internal-repo-manager</id>
      <name>Internal Mirror</name>
      <url>https://repo.example.com/maven2</url>
      <mirrorOf>*</mirrorOf>
    </mirror>
  </mirrors>
</settings>Code language: HTML, XML (xml)

Note: The mirror snippet is a generic Maven pattern shown for context. The original post only states that beta-1 needed a mirror declaration and beta-2 removed that need in the described scenario.

Best practices for legacy Sonar and Maven setups

• Confirm your Sonar server version first; the cited improvement applies to 2.2+.
• If behavior differs across environments, compare effective Maven settings and mirror resolution.
• Document whether your build relies on historical plugin behavior before upgrading any scanning components.
• Treat this release note as historical context and validate against your current SonarQube/Maven documentation.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.