[BUILD-589] Allow released versions of SNAPSHOTs to be resolved from the staging repository Created: 17/Nov/21 Updated: 29/Nov/21 Resolved: 29/Nov/21 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | POMs 43 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Maxime Michel |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Epic Link: | Release automation | ||||||||
| Description |
|
When running the following command: mvn versions:update-properties -DallowIncrementalUpdates=false -DallowMajorUpdates=false -DallowMinorUpdates=false -DgenerateBackupPoms=false -Pstaging With PPOM 42, a SNAPSHOT such as main 6.2.13-SNAPSHOT won't be converted into 6.2.13 (even when in staging). This is because our configuration for the staging repository has the property snapshots.enabled = false. This means that, in some cases (TBD), Maven won't even try to look for a possible next version, because the initial version is a SNAPSHOT to begin with. This ticket also includes filtering out debug versions such as 6.2.13- |