Maven projects no longer get made-up dependencies
- What was broken
- graphify read every dependency listed anywhere in a Maven pom file, including version pins and plugin dependencies. A parent project that only pins versions showed up as depending on all its modules.
- What I changed
- Only the dependencies a project really declares, at the top level or in a profile, become links in the graph.
- Why it matters
- The graph of a multi-module Java build shows how its parts really depend on each other.
see the code, #4596 (opens in a new tab)closed on GitHub, landed as a commit (opens in a new tab)