Join GitHub today
Re-think pom and project structure #455
According to https://github.com/spring-projects/spring-boot/wiki/Building-On-Spring-Boot#dependency-management third party projects (like Joinfaces in this case) should not require another parent-pom, but just provide a
#384 was a first step in this direction, but Joinfaces still provides a parent pom and our maven example projects still use it.
Even if we wan't to keep the parent pom for external usage, we should clearly separate what we want to export to projects using Joinfaces and what is "Joinfaces-internal" and should not be exported.
I use joinfaces configuration from joinfaces-parent regularly on external projects, not only internal usage.
How could I reuse profiles (checkstyle, findbugs, cpd, pmd, duplicate) and properties (ex.: mojarra.version, primefaces.version) without using parent pom?