jgitver / jgitver/jgitver-maven-plugin

Make useGitCommitTimestamp use commit timestamp instead of author timestamp

Aperta
#167 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Groovy
Stelle
166
Fork
42
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

## Issue

**version**: 1.9.0
**usage context**:
- [x] maven command line: 3.8.3

**Problem description**:

One reason for adding a timestamp to the version is that you want to have strictly increasing versions, where you can easily see which of two given versions is the newer one.

Currently, `useGitCommitTimestamp` is using the author timestamp of the commit. This is the timestamp that tells you when the author created the commit.
Then there is the commit timestamp, which is the timestamp that tells you when the commit was pushed.

Using the author timestamp as a version is a problem, because you do not gete strictly increasing versions. If I merge a PR that I have been working on for a couple of months, the version will look like it is two months old. But in fact it is the latest version, merged just a few seconds ago.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

The issue identifies useGitCommitTimestamp as the entry point and Maven command-line versioning as the usage context, but names no files or tests. Start by searching the repository for useGitCommitTimestamp and the Git timestamp retrieval, then verify that generated versions use the commit timestamp and remain increasing after merged changes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
git, groovy
Ambito
build-system, release
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.