I don't have experience with this. Why exactly does all code need to be together?
Quintin Beukes On Tue, Sep 29, 2009 at 10:38 AM, ifsNabble <[email protected]> wrote: > > Hi Quintin, > > I´m starting automatic build in Hudson with Maven target "mvn compile". > Then all tests are run and with Sonar-Plugin the code quality is anlyzed and > published in Sonar. > The quality metrics rely on JUnit (-> Surefire), PMD, Cobertura etc. and > some specialties where object coupling, depth of inheritance tree etc. is > computed. > And for these special metrics I need all code together during compilation. > > Ralf > > > Quintin Beukes-2 wrote: >> >> Yes, writing an ant script that merges projects into a temporary place >> is an ugly solution. >> >> What are you using for the code quality analysis? >> >> Quintin Beukes >> >> >> >> On Tue, Sep 29, 2009 at 10:24 AM, ifsNabble >> <[email protected]> wrote: >>> >>> Hi all! >>> >>> I´m stuck with following problem: >>> >>> My Project consists of about 150 Maven projects. All of them are somehow >>> dependent on each other. >>> I´m able to build and analyze code quality for every single project. >>> But to analyze special metrics I need all source code together in one >>> folder. And there´s my problem. >>> >>> I could create a stupid dummy ant script that copies every code from >>> /src/main/java to the common source folder. And then I start analyzing >>> this. >>> But that´s not really what I want. Apart from that I do need a new >>> pom.xml >>> for the new all-embracing project. And then I´m at the point where I have >>> to >>> copy/paste the source code from the single projects to the "big" project. >>> >>> I thought about using module for solving my problem, but I don´t know if >>> that suits my needs? >>> >>> I´m using Eclipse and m2eclipse-Plugin, Hudson as build tool and Sonar as >>> code quality analyzer. >>> Our platform is Windows. >>> >>> Does anyone have some suggestions or best practices for my problem? >>> I´m sure I´m not the first one facing such problems. >>> >>> The main pre-conditions for the solution are: >>> - I don´t want to change the structure of my projects (e.g. merge some >>> projects together) >>> - I´d like to use as many native Maven tools as possible (plugins, >>> techniques like modules, ...) and avoid using handmade solutions like >>> copy&paste or writing ant scripts >>> >>> Thanks already! >>> -- >>> View this message in context: >>> http://www.nabble.com/How-to-implement-Code-Quality-Analysis-on-multiple-Maven-Projects--tp25658865p25658865.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] >>> >>> >> >> --------------------------------------------------------------------- >> 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--tp25658865p25659063.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
