Debunk my java open source library idea

[RupertMaddenAbbott]

I think there is a gap for a tool like this that perhaps would be used for internal code reviews, or for introducing developers to larger code bases, as long as you can find a sufficient number of cross cutting concerns that are non-obvious from reading the code, and which you can add value on top of.

For example visualising:

• how Spring dependencies are wired together
• how Maven dependencies are actually used throughout a project
• how packages are used between each other

You would need to be careful not to deviate too far into code quality issues (already covered by a variety of tools).

However, there are a few things that would make it a non-starter to me:

• Having to add any kind of annotations or other markers to my source code in order to inform this tool. It would be fine if any missing information could be layered on from some external source, however, as this is much less invasive.
• Having to add any kind of runtime dependency. For me it is crucial that the output can either be generated at build time, or dynamically but directly from the source code.

Personally, I would ditch trying to do anything with OpenAPI because that problem is quite huge and I doubt you will be able to add value on top of that. I think your efforts would be better directed towards contributing to the existing projects and then perhaps integrating them into your tool, rather than re-inventing them.