We use our own framework in our company, which is based on Spring and Wicket. The framework has a total of two artifacts:
- our-framework-parent, which derives from spring-boot-dependencies in order to benefit from the dependency management of Spring boot
- our-framework, which is derived from our-framework-parent and contains the wicket components (footer, header...), Spring base components (auth, filter, webconfig...).
Our repositories then derive from our-framework-parent and have our-framework as dependency (version is determined via the our-framework-parent).
We would now like to migrate to Spring Boot. This raises the question of whether we should simply let the our-framework-parent inherit from spring-boot-parent and pack the necessary starters (starter-web, starter-log4j...) directly into our-framework & otherwise leave the structure as it is.
Or should we not use a starter in our framework and instead create another artifact - for example our-framework-spring-boot-autoconfigure and our-framework-spring-boot-starter?
If our framework were not written in Spring, the case would be totally clear to me. Here, docs.spring.io also recommends the use of starters. However, it is completely unclear to me whether I should outsource everything individually in our case.
I look forward to answers.