SonarQube Jenkins

Use sonar:sonar by default and provide a way to specify fixed version

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.4
  • Fix Version/s: 1.6
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently Hudson is running mvn sonar:sonar so we cant really know what will be the version of the sonar-maven-plugin used during the build. In my case it is a snapshot that is used because codehaus snapshot repo is enabled on Nexus.

I would like to have a new configuration option in Hudson sonar plugin to define the version to be used (for example 1.4). In this case you should run:
mvn org.codehaus.mojo:sonar-maven-plugin:1.4:sonar

Thanks

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Evgeny Mandrikov added a comment -

FYI, I've replaced "sonar:sonar" by "org.codehaus.mojo:sonar-maven-plugin:1.0-beta-1:sonar" in r30218.
Is it enough? I (and Simon) think that it is enough, because sonar-maven-plugin just a bootstrapper for real plugin.
Or you can provide more exotic use case?

Show
Evgeny Mandrikov added a comment - FYI, I've replaced "sonar:sonar" by "org.codehaus.mojo:sonar-maven-plugin:1.0-beta-1:sonar" in r30218 . Is it enough? I (and Simon) think that it is enough, because sonar-maven-plugin just a bootstrapper for real plugin. Or you can provide more exotic use case?
Hide
Permalink
Julien HENRY added a comment -

It is enough as long as I don't want to test the snapshot version for Maven 3 for example. It will do the trick for now but I really suggest you add a parameter to allow to change version of the plugin (default value should be 1.0-beta-1).

Show
Julien HENRY added a comment - It is enough as long as I don't want to test the snapshot version for Maven 3 for example. It will do the trick for now but I really suggest you add a parameter to allow to change version of the plugin (default value should be 1.0-beta-1).
Hide
Permalink
Evgeny Mandrikov added a comment -

We are working on it. But support for mvn3 will be later.

Show
Evgeny Mandrikov added a comment - We are working on it. But support for mvn3 will be later.
Hide
Permalink
Evgeny Mandrikov added a comment -

Today at SonarSource we decided to use "sonar:sonar" by default and provide a way to specify fixed version.

Show
Evgeny Mandrikov added a comment - Today at SonarSource we decided to use "sonar:sonar" by default and provide a way to specify fixed version.
Hide
Permalink
Evgeny Mandrikov added a comment -

Implemented in r33072.

Show
Evgeny Mandrikov added a comment - Implemented in r33072.
Hide
Permalink
Stéphane Nicoll added a comment -

Could you please release 1.6? We have the same issue and it's quite annoying.

Thanks!

Show
Stéphane Nicoll added a comment - Could you please release 1.6? We have the same issue and it's quite annoying. Thanks!
Hide
Permalink
Evgeny Mandrikov added a comment -

Hi Stephane,
Don't worry - we are going to release next version in few days.

Show
Evgeny Mandrikov added a comment - Hi Stephane, Don't worry - we are going to release next version in few days.
Hide
Permalink
cforce added a comment -

Please release 1.6. i also get mad with this problem!

Show
cforce added a comment - Please release 1.6. i also get mad with this problem!
Hide
Permalink
cforce added a comment -

A more exotic use case is btw when using the plugin to analyze none maven projects, where the pom is created by the plugin isetlf? and you can't set any versions.

Show
cforce added a comment - A more exotic use case is btw when using the plugin to analyze none maven projects, where the pom is created by the plugin isetlf? and you can't set any versions.
Hide
Permalink
Stéphane Nicoll added a comment -

why are we talking about "org.codehaus.mojo:sonar-maven-plugin:1.0-beta-1" in this thread while this is not the groupId for recent versions. I just upgrade to 2.5 and 1.6.1 and when I specifiy 2.5 as version in the plugin configuration, it invokes the following "org.codehaus.mojo:sonar-maven-plugin:2.5:sonar"

which of course does not exist in any repository out there. Does anybody knows why org.codehaus.mojo is used in thread of org.codehaus.sonar? Could that be a corrupted metadata somewhere?

We have the issues for months now and it's driving me nuts.

Thanks

Show
Stéphane Nicoll added a comment - why are we talking about "org.codehaus.mojo:sonar-maven-plugin:1.0-beta-1" in this thread while this is not the groupId for recent versions. I just upgrade to 2.5 and 1.6.1 and when I specifiy 2.5 as version in the plugin configuration, it invokes the following "org.codehaus.mojo:sonar-maven-plugin:2.5:sonar" which of course does not exist in any repository out there. Does anybody knows why org.codehaus.mojo is used in thread of org.codehaus.sonar? Could that be a corrupted metadata somewhere? We have the issues for months now and it's driving me nuts. Thanks
Hide
Permalink
Stéphane Nicoll added a comment -

BTW, if I execute mvn sonar:sonar on the command line (outside sonar) it just runs fine with the same config (same repo, etc).

Show
Stéphane Nicoll added a comment - BTW, if I execute mvn sonar:sonar on the command line (outside sonar) it just runs fine with the same config (same repo, etc).
Hide
Permalink
Evgeny Mandrikov added a comment -

Hi,

Version of Sonar Mojo is not the same as version of Sonar Server. And no need to update this version with each update of Server - this is a main goal of Mojo.
So just keep this field in Hudson empty and "mvn sonar:sonar" would be executed.

P.S. in future it's better to use users mailing list (http://www.sonarsource.org/support/support/) to get support.

Show
Evgeny Mandrikov added a comment - Hi, Version of Sonar Mojo is not the same as version of Sonar Server. And no need to update this version with each update of Server - this is a main goal of Mojo. So just keep this field in Hudson empty and "mvn sonar:sonar" would be executed. P.S. in future it's better to use users mailing list ( http://www.sonarsource.org/support/support/ ) to get support.
Hide
Permalink
Julien HENRY added a comment -

As this question is very frequent, I have added an entry in the FAQ: http://docs.codehaus.org/display/SONAR/Frequently+Asked+Questions#FrequentlyAskedQuestions-Whatisthedifferencebetweenorg.codehaus.mojo%3Asonarmavenpluginandorg.codehaus.sonar%3Asonarmavenplugin%3F

Show
Julien HENRY added a comment - As this question is very frequent, I have added an entry in the FAQ: http://docs.codehaus.org/display/SONAR/Frequently+Asked+Questions#FrequentlyAskedQuestions-Whatisthedifferencebetweenorg.codehaus.mojo%3Asonarmavenpluginandorg.codehaus.sonar%3Asonarmavenplugin%3F
Hide
Permalink
Evgeny Mandrikov added a comment -

Julien, thanks for your effort.

Show
Evgeny Mandrikov added a comment - Julien, thanks for your effort.

People

  • Assignee:
    Evgeny Mandrikov
    Reporter:
    Julien HENRY
Vote (0)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: