Currently, we collect all poms in one repository, but technically, we deploy all poms as individual artifacts. This is tricky, because during a release on GitHub, all deployments will fail for poms, which version numbers have not been increased.
That will cause the Travis build to fail as well, which is an undesired property. So either we go for an single pom - single repo approach or we ship all poms as bundle. That means all poms will receive a new common version tag, the tag of the bundle release, regardless if a single pom was changed or not.
The latter is pretty straightforward to implement using maven properties to propagate the version number in all poms.
sven1103
commented
5 years ago
Currently, we collect all poms in one repository, but technically, we deploy all poms as individual artifacts. This is tricky, because during a release on GitHub, all deployments will fail for poms, which version numbers have not been increased.
That will cause the Travis build to fail as well, which is an undesired property. So either we go for an single pom - single repo approach or we ship all poms as bundle. That means all poms will receive a new common version tag, the tag of the bundle release, regardless if a single pom was changed or not.
The latter is pretty straightforward to implement using maven properties to propagate the version number in all poms.