Sonar

work in progress rev 11395.
but npe in pico

Caused by: java.lang.NullPointerException
        at org.picocontainer.DefaultPicoContainer.addComponent(DefaultPicoContainer.java:441)
        at org.picocontainer.DefaultPicoContainer.access$400(DefaultPicoContainer.java:78)
        at org.picocontainer.DefaultPicoContainer$AsPropertiesPicoContainer.addComponent(DefaultPicoContainer.java:1023)
        at org.sonar.batch.BatchMojo.createMainContainer(BatchMojo.java:157)
        at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:135)
        at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
        at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:113)

code in branh https://svn.codehaus.org/mojo/branches/sonar-maven-plugin-mvn-3.x

The mojo is just a bootstrapper. It installs and executes the sonar-core-maven-plugin, deployed into the sonar server.
This one has to be upgraded to Maven 3 too, because it executes other maven plugins like checkstyle or cobertura. In order to be compatible with both maven 2.x and 3.x versions, I think we should :

• extract all core classes of sonar-core-maven-plugin in a new module called sonar-batch.
• create a sonar-core-maven3-plugin, depending on sonar-batch.

Both sonar-core-maven-plugin and sonar-core-maven3-plugin are deployed when starting sonar. The first one is executed by the current version of the sonar mojo (1.0-beta-1), the second one by the version 2.0.

Not sure I've been understandable !

I come back to you when the modifications described in the previous comment are done.

Olivier Lamy fixed an issue with maven 3 classloader. We're waiting now for the release of maven-checkstyle-plugin 2.5 (see MCHECKSTYLE-123)

sure I will try to cut this release ASAP.

Thank you, it's done.

It is great to see activity here! Is there actually a roadmap on when full Maven 3 support will be available? How far are you along the road? What are the big issues currently?

We still have an issue with custom checkstyle rules. I'm not sure we'll have enough time to fix it for release 2.0 but for 2.1.

Just FYI: I'm working with sonar-maven-plugin from branch about a week and it works fine. But of course I don't use custom rules.

is it due to an issue in checkstyle plugin ?

No, the problem comes from the way Sonar adds dependencies to maven plugins at runtime.
The configuration of maven plugins (including version to use, parameters and additional dependencies) is added at runtime to the current maven session. It works well in major cases, except for additional deps when the target plugin is already defined in the initial pom.

Is the last version available somewhere as a binary?

For now not.

The Sonar maven plugin hosted at Codehaus Mojo is still not compatible with Maven 3. To benefit from this feature, build the trunk and execute

mvn org.codehaus.sonar:sonar-maven3-plugin:2.2-SNAPSHOT:sonar

For information it supports maven 3.0-beta-1 but not alpha versions.

Dependencies between Maven modules are lost in the 'Design' service when analyzing Maven multi-modules project with Maven 3 and Sonar 2.2. But the content of the 'Libraries' service is correct.

The Codehaus Mojo is not updated, so the shortcut mvn sonar:sonar still does not work. The temporary workaround is to execute this command-line for maven 3 : mvn org.codehaus.sonar:sonar-maven3-plugin:2.2:sonar

I am seeing this same error with Maven 3.0 Beta.

I do confirm that the following command line works with maven 3-beta3 :

mvn org.codehaus.sonar:sonar-maven3-plugin:2.2:sonar

To be able to launch the standard command "mvn sonar:sonar", the ticket MOJO-1545 needs to be fixed.

Hi,

I'm getting this exact same error. I'm on Sonar 2.2 and Maven 3.0 final. Anything I should do/check? Thanks

You should use org.codehaus.sonar:sonar-maven3-plugin instead of org.codehaus.mojo:sonar-maven-plugin or see SONAR-1851.

Thanks Evgeny