Of course! Here´s the solution we found for our problem:
As described we have the structure
/trunk/projectA/pom.xml
/trunk/projectAB/pom.xml
/trunk/project.../pom.xml
/trunk/projectZ/pom.xml
That makes us able to put a pom.xml in the highest hierarchy folder
(/trunk/pom.xml).
This pom.xml uses the maven-build-helper-plugin where you can specify
additional source folders.
And due to the fact that we´re on top of folder hierarchy we can use the
subfolders ("/project.../src/main/java") and create in that way a virtual
project with many many source folders.
The metrics we use work. we are now able to compute complexity of code or
inheritance and so on.
We now found out that we have about 860000 lines of code!
But some thing are still not possible: running JUnit tests for JUnit reports
or code coverage isn´t possible, because of the huge amount of test classes
we have. This would blow up our build server - or would last some weeks.
I hope you have an idea how it works.
Cheers
baerrach wrote:
>
> On Wed, Sep 30, 2009 at 10:53 PM, ifsNabble
> <[email protected]> wrote:
>>
>> 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.
>
> Can you supply detailed steps to educate future mailing list searches
> with similar problems.
>
> Cheers
>
> ---------------------------------------------------------------------
> 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--tp25658865p25734856.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]
