If we change the docs-build pom to use spring-cloud-build as a parent we can eliminate a lot of overhead of maintaining the POM in two different branches for each project.
The only change would be we would need to activate the docs profile when running ./mvnw antora (which we currently do not have to do).
I have consolidatated some of what is used in this POM to our
spring-cloud-build
POM which we needed there anyways.See https://github.com/spring-cloud/spring-cloud-build/blob/24ad0c7042234b7668a66b531940a0adfd1fd60a/pom.xml#L1070-L1092
If we change the
docs-build
pom to usespring-cloud-build
as a parent we can eliminate a lot of overhead of maintaining the POM in two different branches for each project.The only change would be we would need to activate the
docs
profile when running./mvnw antora
(which we currently do not have to do).