maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MRELEASE-817) When tagging using git give an appropriate message
Date Tue, 12 Jan 2016 20:12:42 GMT

     [ https://issues.apache.org/jira/browse/MRELEASE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MRELEASE-817.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still persists, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> When tagging using git give an appropriate message
> --------------------------------------------------
>
>                 Key: MRELEASE-817
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-817
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.3.2, 2.4
>         Environment: All
>            Reporter: Fred Cooke
>            Priority: Minor
>
> "copy for tag 0.4" is plain wrong for git. The message should be more like "Version X.Y.Z
tagged by m-rel-p" or something to that effect.
> Perhaps configurable, or maybe even prompt for it, or pull it from a defined file. This
is what I do in my GNU-Make-maven-release-clone such that I can enter a meaningful description
of what is in the release, as part of the tag object. I open a new temp file with vim and
use the saved file as the tag message. Maven could optionally prompt for it just as it does
for the versions itself.
> In git these are known as annotated tags, and are something that SVN simply does not
have. The plugin is already using annotated tags, it's just that the annotation itself is
poor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message