Hi Freddy, thanks for the hint. But fortunately we don´t use Checkstyle.
By the way: with this plugin we are able to the stuff we want. My colleague tested it and it worked. Ralf Freddy Mallet wrote: > > Hi Ralf, > > FYI, the Sonar Core and most underlying Maven Quality plugins are > compatible > with the use of the Maven Build Helper Plugin but this is not the case of > the Maven Checkstyle plugin : > http://jira.codehaus.org/browse/MCHECKSTYLE-70. > > > Freddy > > ---------------------------------------- > Freddy Mallet > www.SonarSource.com > Sonar.codehaus.org > http://twitter.com/FreddyMallet > ---------------------------------------- > > > On Wed, Sep 30, 2009 at 6:56 AM, ifsNabble > <[email protected]>wrote: > >> >> The analysis is done by Sonar which takes all the configured reports and >> the >> source code. >> Based on the compiled source the JDepend metrics are computed, based on >> Cobertura report (created by maven plugin) the code coverage is computed >> and >> so on... >> >> Regarding your classpath hint: >> I found another Maven plugin (build-helper-maven-plugin) which does >> something like that. You can configure different source folders within >> this >> plugin. >> Maybe this can be a somehow generic way to do the task without >> copying&pasting code from one project to another. >> >> Our layout is >> SVN - trunk - projectA - src - main - java >> SVN - trunk - projectB - src - main - java >> ... >> >> When placing a pom.xml in >> SVN - trunk - pom.xml (above all other projects) >> I ´m able to define with the maven-helper-plugin some source folders like >> that: >> <plugin> >> <groupId>org.codehaus.mojo</groupId> >> <artifactId>build-helper-maven-plugin</artifactId> >> <version>1.1</version> >> <executions> >> <execution> >> <id>add-source</id> >> <phase>generate-sources</phase> >> <goals> >> <goal>add-source</goal> >> </goals> >> <configuration> >> <sources> >> <source>projcetA/src/main/java/</source> >> <source>projectB/src/main/java/</source> >> </sources> >> </configuration> >> </execution> >> </executions> >> </plugin> >> >> Maybe that works!? >> A colleague of mine will find it out. >> >> >> Quintin Beukes-2 wrote: >> > >> > OK, I understand. >> > >> > Of all those software systems you mentioned. Which one of them does >> > the actual analysis? doesn't it have a feature to specify more >> > classpaths? >> > >> > Quintin Beukes >> > >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/How-to-implement-Code-Quality-Analysis-on-multiple-Maven-Projects--tp25658865p25675029.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- View this message in context: http://www.nabble.com/How-to-implement-Code-Quality-Analysis-on-multiple-Maven-Projects--tp25658865p25680960.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
