[BUILD-436] Update parent pom automatically in modules Created: 27/Jan/21  Updated: 27/Jan/21

Status: Selected
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Šimon Demočko Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by BUILD-435 Remove clover license from global mav... Open
Template:
Acceptance criteria:
Empty

 Description   

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.

Generated at Sun Feb 11 23:41:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.