Proper multi-module maven project structure
forgedhallpass opened this issue · comments
The application lacks a proper maven project structure.
There should be a parent POM that would contain:
- the other sub-modules
- extracted versions of relevant dependencies across the project
- dependency management
- plugin management
- etc
Creating the proper structure would:
- reduce code duplication
- enable opening the project without the need of custom IDE configurations
- enable building the whole project at once
All the other maven modules should be named and configured in a unified way (including package names etc).
The project should be easily deployable, properly testable and in sync with the maven lifecycle phases (creation of maven profiles might be required)
The project should be IDE agnostic.