|
Otherwise, some environment changes could break old modules depending on old parent pom.
Example
- BUILD-435 removal of clover license after moving to open-source clover would not allow older modules depending on the old parent pom to run coverage -> they would still depend on old clover for which the license wouldn't be present anymore. This requires manually updating parent pom in many old untouched modules manually.
Solution contours
- Automatically raise ppom ver. in all modules depending on it after a new version is created
- This to ensure that problems with raising the version are caught sooner than during release (which is currently the time when ppom version bumping takes place)
- Not sure if opening PRs would be a good idea though -> this could generate a lot of noise. Usually, for ppom version bumping we did direct commits, maybe we could do it like this as well en mass.
|