Hi, Not sure what you mean. Do you have many modules in the same multimodule project that have the same artifactId ? If so, then you have a more important issue than the sonar one. I'm even surprised Maven accepts to load it. Should be checked in Maven sources, but I guess artifactId must be unique in a multimodule build.
>From a more general POV, I would advice to also have artifactId being universally unique. It might seem counter-intuitive if you believe groupId is enough to make the difference between two artifacts, but there are several situations where you'll be stuck if you don't strictly follow this rule (web-inf/lib jar files overwriting being one obvious example). Cheers 2014/1/20 Kai Zimmermann <zimmerman...@gmail.com> > Hello, > > I'm playing with sonar:sonar and the sonar.skippedModules property in a > reactor build. In lack of documentation, I tried to use the module name > (directory where te project is), but it doesn't work. So I changed it to > the artifactId and now it works. > > My question: is it luck that it works and it really have to be the > artifactId? Because then I have a problem, because the artifactId is not > unique! Would be the module paths better? > > Kai > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! nbsp;! >
