[FOLIO-3015] Ensure semantic versioning number obtained from Maven POM Created: 15/Feb/21 Updated: 15/Feb/21 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | David Crossley | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | FOLIO DevOps |
| Description |
|
Various of the new Spring Way modules (e.g. see FOLIO-3001 comment) have used non-semantic version numbers. The "Implementation versions" must use semantic versioning, as major.minor.bugfix Refer to https://dev.folio.org/guidelines/contributing/#version-numbers In CI, the module version is extracted from the POM via jenkins-pipeline-libs/vars/setEnvMvn |