Stefan Ferstl

The 4.0.x version has not many changes in the code that was already there. You can find a complete List here: https://github.com/ferstl/depgraph-maven-plugin/releases/tag/depgraph-maven-plugin-4.0.0 . Since you are planning to switch to...

Version 4.0.2 is released and available on Maven Central

Hi, never heard about it but looks interesting and not so difficult to adapt. I‘ll keep this issue open but I probably won‘t be able to work on it for...

Hi @mmoser18 Based on your description of your problem, it seems that you are using the [depgraph:graph](https://ferstl.github.io/depgraph-maven-plugin/graph-mojo.html) goal of the plugin. When run on a multi-module project it will create...

Hi, Do you have an example where this problem occurs? Version 3.3.1 fixed a problem with circular dependencies. But these did only occur when the `showConflicts` flag was enabled.

> We could reproduce the Problem in a dummy-project. That would be nice for debugging. If I understand you correctly, your `very-important-project` looks something like this: ``` very-important-project - some-dependency-in-test-scope...

Hi @gabrielrussoc The versions are indeed ignored in the aggregated graphs. My intention for that was to mimic an overall dependency graph on a multi-module maven project. Choosing only the...

Hi @glianeric, Would the {{graph}} goal help in your case? It creates a dependency graph for each individual module.

The plugin uses Maven's default notation for single-line artifact IDs and the standard filtering mechanisms. I just took a look at the implementation and possibly you can use a version...

This is not possible to achieve with the current filtering options. This would require some kind of option to "cut off" the transitive dependencies of a certain artifact, i.e. something...