Hi, the problem with JDepend plugin is :
All design quality metrics are computed into a single project, not with other modules which could use this first project. So the Afferent and Efferent Couplings metrics are distorted with this problem. The dashboard plugin cannot resolve this lack. Brad Harper wrote: > > Does anyone have experience running the JDepend reporting plugin in a > multi-module project? > > We've been able to successfully run the subject plugin [via site:site] > in individual projects with <packaging> types of jar and war, but when > performing > > mvn jdepend:generate > > in the top-level project [which contains no source of its own], the > plugin fails with > > ... > [INFO] [jdepend:generate] > Directory does not exist: c:\workspace\dev\target\classes > ... > > Ultimately, the goal is to run 'site:site' for the top-level project > [which would run JDepend and other reporting plugins], followed by > 'dashboard:dashboard'. > > BTW, there isn't any configuration info > http://mojo.codehaus.org/jdepend-maven-plugin/. > > Thanks. > > Brad > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/JDepend-Reporting-Plugin-in-a-Multi-Module-Project-tp20980649p21011352.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]
