[
http://jira.codehaus.org/browse/MOJO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89386
]
Stefan Seidel commented on MOJO-676:
------------------------------------
I think the first option would be better, but I don't know about the activity
there. The JDepend site has last been updated 07/27/2006.
The second options should not bee too complicated, I think. For a first step
that should be enough, although we may need to read the plugin settings from
pom.xml - which could become quite an effort.
> JDepend Summary should show efferent, not afferent couplings
> ------------------------------------------------------------
>
> Key: MOJO-676
> URL: http://jira.codehaus.org/browse/MOJO-676
> Project: Mojo
> Issue Type: Improvement
> Components: dashboard
> Reporter: Stefan Seidel
>
> As the calculation of the afferent coupling is doomed to be incomplete with
> multi-module projects (because the classes using this modules classes might
> be outside the module itself), it makes little sense to show it. Efferent
> coupling however is independent of other projects an is thus "more faithful
> to the truth" ;)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
