Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty Graph because of an circular dependency? #154

Open
Gerrri opened this issue Apr 25, 2022 · 4 comments
Open

Empty Graph because of an circular dependency? #154

Gerrri opened this issue Apr 25, 2022 · 4 comments
Labels

Comments

@Gerrri
Copy link

Gerrri commented Apr 25, 2022

We found out that the dependency graph is empty (see below) in projects where an circular dependency exists.
Is this an known issue or is there any workarround for that, or are we just too stupid to use the tool? 😄

[INFO] --- depgraph-maven-plugin:4.0.1:for-artifact (default-cli) @ standalone-pom ---
[INFO] Dependency graph:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
@ferstl
Copy link
Owner

ferstl commented Apr 25, 2022

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.

@Gerrri
Copy link
Author

Gerrri commented Apr 26, 2022

Hi and sorry for the limited information.

We have run this command:
mvn com.github.ferstl:depgraph-maven-plugin:3.3.0:for-artifact -DgroupId=great.group.id -DartifactId=very-important-project -Dversion=1.0.0 -DgraphFormat=text -DshowGroupIds=true -DshowVersions=true

We could reproduce the Problem in a dummy-project.
The empty graph appears, when the project only has one dependency in scope:test and in this dependency there is a circular dependency.

If you need further information, let me know :)

@ferstl
Copy link
Owner

ferstl commented Apr 26, 2022

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
  - very-important-project
    -...

One other question: The very-important-project is an external artifact and you run the for-artifact goal without a maven project, correct? If you want to create graphs within a Maven project, you should use graph or the aggregate-* goals.

@Gerrri
Copy link
Author

Gerrri commented Apr 26, 2022

Yes, its an external artifact and there is no maven project.

The Structure is:

very-important-project
- some-dependency-in-test-scope
  -  antoher-dependeny
    - some-dependency-in-test-scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants