Java Stacks: multi module structure ADR update #1480
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Java Stacks: multi module structure
📲 What
We are restructuring Java Stacks repository into a monolithic architecture that consolidates all necessary code for our stacks modules.
🤔 Why
This change is driven by the need for a more streamlined and efficient development process. By centralising the codebase, we can better manage dependencies, reduce redundancy, and simplify the build process. This approach is based on an Architectural Decision Record (ADR): https://amidodevelopment.atlassian.net/wiki/spaces/TEC/pages/3793256449/ADR+Java+4036+Java+Modular+Development+Deployment that outlines the benefits of a monolithic structure for our specific use case.
🛠 How
We will update the Java stack repository to a monolithic structure that includes all required code for the stacks module. This will be achieved using a combination of Spring profiles, Manifold, and a customised Maven plugin. At compile time, running mvn compile will generate a new project with the necessary configuration and code.