[
http://jira.codehaus.org/browse/MOJO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89373
]
Stefan Seidel commented on MOJO-676:
------------------------------------
In theory, yes, But take this example:
{code}
+--parent
+--childA
+--org.codehaus.a.classA (imports java.util.*, java.io.*)
+--childB
+--org.codehaus.b.classB (imports org.codehaus.a.*)
{code}
Now JDepend says:
{code}
module |Ce |Ca
-------+---+---
classA | 2 | 0
classB | 1 | 0
{code}
And the information gained from Dashboard is Ca=0 in every case, which is
misleading because in reality Ca is 1 for org.codehaus.a.classA, whereas Ce is
correct.
Am I right there?
Unfortunately, I don't see how to calculate Ca globally (& truthfully) without
running JDepend on all source paths. After all, it *might* be possible to
collect the java source paths during 1st build, store them in dashboard.xml and
then in 2nd build, run jdepend on all the collected source folders.
> 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
