[BUILD-105] Update to buildnumber 1.3 Created: 22/May/12 Updated: 13/Apr/17 Resolved: 05/Aug/14 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | Poms |
| Affects Version/s: | None |
| Fix Version/s: | POMs 29 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Description |
|
Up to 1.1, Buildnumber plugin's support for Git was half-baked. The branch name was not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 did not help) There are workarounds or alternatives, but unless pressing, I'd rather wait for this to be implemented in the "official" plugin.
|
| Comments |
| Comment by Magnolia International [ 06/May/14 ] |
|
Upgrading to 1.3 makes this work. We could then use ${scmBuildNumber} in license.xml or other resources where we'd need the branch name from where something was built. |