The compatibility with mvn 3.0.x is fixed. Here is the new staging repository: ttps://nexus.codehaus.org/content/repositories/orgcodehausmojo-1004<https://nexus.codehaus.org/content/repositories/orgcodehausmojo-1004>
Thanks Simon Brandhof www.sonarsource.com twitter.com/SimonBrandhof On 31 July 2013 14:47, Simon Brandhof <[email protected]> wrote: > Ok, I better understand. It's a bug. Our integration tests did not execute > this combination. > > To sum up : sonar-maven-plugin 2.1 is supposed to be compatible with : > > - maven 3.0.x and any version of SonarQube > - maven 3.1+ and SonarQube 3.7+ > > In any case the error message should be improved in order to mention > SonarQube 3.7+. > I get back to you when the issue is fixed. > > Thanks for your feedback > Simon > > > > Simon Brandhof > www.sonarsource.com > twitter.com/SimonBrandhof > > > On 31 July 2013 11:11, Baptiste MATHUS <[email protected]> wrote: > >> Hi Simon, >> >> Not sure I get what you mean (we could continue in french, but not sure >> it would be great here ;-)) and if I was cristal clear. >> >> I'm actually currently getting the error although we *don't* use Maven >> 3.1 but 3.0.4. >> So, the message telling me "Sonar[Qube] 3.4.1 does not support Maven 3.1" >> although I'm actually not using 3.1 is quite disturbing. >> >> Is it clearer? >> >> Or, maybe, this plugin version requires maven 3.1+? >> >> Thanks >> >> >> 2013/7/31 Simon Brandhof <[email protected]> >> >>> Hi Baptiste, >>> >>> Exact, this is the expected error. And I agree, the message should tell >>> which minimal version should be used. >>> What about simply replacing the error message with "Maven 3.1+ requires >>> SonarQube 3.7+" ? >>> >>> Thanks >>> <http://twitter.com/SimonBrandhof> >>> >>> >>> On 31 July 2013 10:29, Baptiste MATHUS <[email protected]> wrote: >>> >>>> Hi Simon, >>>> >>>> Just launched a build on our Sonar instance using that plugin, is it >>>> supposed to be backward-compatible? >>>> Here's the failure log: >>>> >>>> >>>> >>>> >>>> [ERROR] Failed to execute goal >>>> org.codehaus.mojo:sonar-maven-plugin:2.1:sonar (default-cli) on project >>>> sup-gfi-cge-parent: SonarQube 3.4.1 does not support Maven 3.1 -> [Help 1] >>>> >>>> >>>> From MSONAR-22, I suppose this might be normal and unsupported? (Btw, I >>>> just realized we never locked down the sonar plugin, that's also why the >>>> upgrade was automatic :-/. I'm gonna have to fix that quickly). >>>> >>>> If so, then I just think the message should be improved since we get >>>> the failure using maven 3.0.4. I suppose in this case it's also meant to >>>> say something along "sonar-maven-plugin:2.1 requires a 3.7+ version >>>> SonarQube", right? >>>> >>>> If so, then I'd be -0.1 on this release to get the error message >>>> improved first since I fear this error is going to happen quite often isn't >>>> it? >>>> >>>> Thanks again for providing this wonderful tool, by the way. >>>> >>>> >>>> >>>> 2013/7/30 Simon Brandhof <[email protected]> >>>> >>>>> Hi, >>>>> >>>>> I'd like to release version 2.1 of sonar-maven-plugin. >>>>> It resolves 4 issues : >>>>> >>>>> * [MSONAR-22] - Support Maven 3.1. Note that it requires SonarQube >>>>> 3.7-RC1 for testing. >>>>> * [MSONAR-26] - Rename Sonar to SonarQube in documentation and fix >>>>> dead links >>>>> * [MSONAR-19] - Log stack trace when server can not be reached >>>>> * [MSONAR-14] - Fix PMD violation >>>>> >>>>> Staging Repository: >>>>> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-1003 >>>>> >>>>> SCM Tag: >>>>> http://svn.codehaus.org/mojo/tags/sonar-maven-plugin-2.1/ >>>>> >>>>> The vote is open for 72 hours and will succeed by lazy consensus. >>>>> >>>>> Thank you very much >>>>> >>>>> -- >>>>> Baptiste <Batmat> MATHUS - http://batmat.net >>>>> Sauvez un arbre, >>>>> Mangez un castor ! nbsp;! >>>>> >>>> >>> >> >> >> -- >> Baptiste <Batmat> MATHUS - http://batmat.net >> Sauvez un arbre, >> Mangez un castor ! >> > >
