Generate only package dependecies

[Chrisposure]

Hi Jens,

thanks for the great Tool!

I am curious if there is or will there be a possibility to only generate dependencies on a given package level.

Thank you,
Christian

[schauder]

Not sure if I understand what you mean something like combining

org.mydomain.stuff.more.stuff
org.mydomain.stuff.more
org.mydomain.stuff

all into org.mydomain.stuff

That you can do already. A slicing pattern of `"org.mydomain.(*)**" should put all of the above into one slice "stuff".

[Chrisposure]

Our application is devided in sub projects, where each one creates a jar file. The question we like to answer is how these jar files are dependend from each other. The generated graphml file is way to big to analyze. So the question that came up was, if there is a way to generate only the dependencies for packages on a given package level (or generate all deps and cut out classes and some packages).

For example: Given are 3 Jars with the following packages:

org.mydomain.pkg.1.sub.ClassA
org.mydomain.pkg.2.sub.ClassB
org.mydomain.pkg.3.sub.ClassC

In the config file I somehow say:

onlyPackageDependency = true
packageLevel = org.mydomain.pkg.*

The result is a graphml file that only shows the packages up to the "packageLevel" and their dependency to each other.

org.mydomain.pkg.1 --depends on--> org.mydomain.pkg.2
org.mydomain.pkg.3 --depends on--> org.mydomain.pkg.2

I hope I could express my question.

[schauder]

Ok, I understand now. Makes sense.

Degraph currently does not support this.

[TomasMikula]

Hi, and thanks for the great tool!

I would also like to limit the graph to only package nodes and dependencies between them (no additional "package level" restriction needed).