Export information about found dependencies about degraph HOT 6 CLOSED

There are already tools doing a good job on the metric side. For example Sonar. I certainly don't want to compete with those.

But there are certain things I could imagine:

• output some statistic as part of the run, just so one can get a quick idea of how much got analyzed. This might be helpfull for getting started when people often seem to analyze all their libraries (hibernate, java, spring, scala ...), resulting in bad performance and unusable huge graphs. This also should be easy to do.
• I guess a sonar plugin (or direct plugin for CI-servers) to count the number of constraint violations could be interesting and certainly possible once it is possible to define constraints (which it actually is right now on the master branch).

Would any of these fit your needs? If yes, which, if not what else?

from degraph.

I think what I had in mind can be implemented as a plugin for an existing software running a CI-server. To this software, Degraph should only contribute what it can analyze best: amount of cyclic dependencies. All the other metrics should be delivered by other plugins / the CI-software itself. I don't know Sonar, Hudson etc that good, but I imagine a Degraph plugin that enables a nice graph with the amount of cycl. dependencies within Sonar etc.

from degraph.

So the metric part will eventually happen. There is already an issue for that: #11

What I will do is offer a way to print out some basic stats as part of the console app.

from degraph.

You may have a look at: http://www.hello2morrow.com/products/sonargraph
There are plugins for sonar and for some IDEs too. I am not quite sure, but there may be a plugin for jenkins / hudson. But this isn't really necessary, 'cause sonar can be triggered by jenkins and because there is a plugin for sonar, you also see the cyclic dependencies after every build in sonar.

from degraph.

Hi everybody: this task is only about some short feed back on stdout about the amount of stuff analyzed. For a discussion about if it makes sense to gather metrics with Degraph and what metrics feel free move over to #11

from degraph.

Degraph (command line version) prints outs some very basic stats at the end

from degraph.