Maven sonar:sonar failure for multi-module projects

16 Aug 2012, 1 minute read

After refactoring a small project to manage subversion auth information into multiple Maven modules I started running into what I assume is a fairly common problem: trying to build a child module which depends on an edit applied to a different module which hasn’t been built yet. For some reason the “Set as main project” option has gone from Netbeans 7.2, so I found myself going back to the command line to build each time.

A couple of days later and I’m integrating the project with a local Sonar instance, only to find it fails with a similar message:

[ERROR] Failed to execute goal on project XXXXXXXX: Could not resolve dependencies for project XXXXXXXX:XXXXXXXX:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: XXXXXXXX, XXXXXXXX, XXXXXXXX: Could not find artifact XXXXXXXX:XXXXXXXX:jar:1.0-SNAPSHOT -> [Help 1]

A bit of digging turned up an issue which claims the problem is solved in Maven 3.2, but that didn’t solve it for me.

At least as an interim, packaging the project prior to running the Sonar plugin does the trick, ensuring that the relevant JARs are available for the sonar plugin’s run:

mvn package sonar:sonar

Now the only problem is dealing with all the violations I’ve introduced, Bad Ryan!


Discuss!

Was this post useful? Why not help others find it by sharing on twitter. While you're there, get in touch and let me know what you think!

Using JIRA to manage a skills registry How do you backup a book?

Hi, I'm Ryan

I care about code, building great teams and the community. I run Slate Horse but I'm still a full-stack developer. Previously co-organiser of JSOxford and OxRUG.


Get in touch