Skip to content

graph reports with custom output directory are a hot mess #575

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

Closed
RBusarow opened this issue May 2, 2022 · 0 comments · Fixed by #612
Closed

graph reports with custom output directory are a hot mess #575

RBusarow opened this issue May 2, 2022 · 0 comments · Fixed by #612
Labels
bug Something isn't working

Comments

@RBusarow
Copy link
Member

RBusarow commented May 2, 2022

If graphs output is set to a custom directory, like $rootDir/graphs, then the files for each sub-module are supposed to be put into relative paths from that root directory, like:

./graphs/lib-1/main.dot
./graphs/lib-1/test.dot
./graphs/lib-2/api/main.dot
./graphs/lib-2/api/test.dot
./graphs/lib-2/impl/main.dot
./graphs/lib-2/impl/test.dot

Instead, we get this thing:

./graphs/build/reports/modulecheck/graphs/main.dot
./graphs/build/reports/modulecheck/graphs/test.dot
./graphs/build/reports/modulecheck/graphs/testFixtures.dot

There are two problems:

  1. Every module has the same relative output path (build/reports/modulecheck/graphs/<source set>.dot), so they all just overwrite each other.
  2. The parent directories build/reports/modulecheck/graphs should not be there. This is especially bad because the inclusion of /build/ means that the report will be automatically ignored by many .gitignore files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant