[BUILD-506] Make sure that common projects in recent CLs have a pom.xml issueManagement section Created: 25/Aug/21 Updated: 02/Dec/21 Resolved: 02/Dec/21 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Christoph Meier |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | VN-Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1d 4.5h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Epic Link: | Release automation |
| Comments |
| Comment by Christoph Meier [ 04/Nov/21 ] |
|
Modules to check / adapt are taken from theĀ Magnolia Release Plan spreadsheet. In case the pom-file of a module lacks the tag. The adapted pom is committed to master as QA commit with QA Add <issueManagement/> to pom-file commit message. |
| Comment by Christoph Meier [ 07/Nov/21 ] |
|
SeeĀ List of modules -> checking issueManagement in pom.xml spreadsheet to see which projects were already fine, and for which projects the pom.xml file has been adapted. |