Bug #1368
Project version cannot be defined if a shallow clone is used
| Status: | Resolved | Start date: | 01/29/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Wienke | % Done: | 100% | |
| Category: | Java | |||
| Target version: | rsb-0.9 |
Related issues
Associated revisions
Define the last commit hash using git log instead of git describe.
This ensures that the hash is also present on shallow clones where git describe fails.
refs #1368
History
#1 Updated by J. Wienke about 11 years ago
- Status changed from In Progress to Resolved
- Target version changed from rsb-0.7 to rsb-0.9
- % Done changed from 0 to 100
In 0.7 there was now commit hash at all. So this is fixed now.