Support for multimodule projects

[njuro]

Hey guys, thank you very much for this project, this is exactly something I was looking for.

Would it be possible to add support for multimodule (Gradle) project? I have several modules and when I register the factories and run the build task for the root project, it will fail with:

  Caused by: java.lang.IllegalStateException: Could not register object [ContextDiagnostic[contextLoadStartTime=1754319348764, contextLoadEndTime=1754319358371, contextLoadComplete=true, heapMemoryUsedBytes=52132304, nonHeapMemoryUsedBytes=53504872, availableProcessors=14, totalMemoryBytes=73400320, maxMemoryBytes=805306368, freeMemoryBytes=20757200]] under bean name 'contextDiagnostic': there is already object [ContextDiagnostic[contextLoadStartTime=1754319348764, contextLoadEndTime=1754319358371, contextLoadComplete=true, heapMemoryUsedBytes=52132304, nonHeapMemoryUsedBytes=53504872, availableProcessors=14, totalMemoryBytes=73400320, maxMemoryBytes=805306368, freeMemoryBytes=20757200]] bound

No idea how easy/complicated this would be. Thanks!

[rieckpil]

Hi @njuro, thanks for raising this - I have no experience with multimodule Gradle projects so far but will check if there's a quick win 😊

[dberna2]

Hi @rieckpil @njuro

I’m working with a multi-module Maven project and ran into the same issue.
While debugging, I noticed that the library tries to create the contextDiagnostic bean twice in the class ContextDiagnosticApplicationInitializer.

Could you clarify what the main purpose of this class is? Is it just to gather context information?
Do you think it might make sense to first check whether the bean already exists, or perhaps create multiple beans with a prefix (maybe using the context ID)?

I’m asking because I’d be happy to help explore a fix if this approach would be appropriate. 😃