You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/03/12 13:38:00 UTC

[jira] [Closed] (MRELEASE-1078) Support version policy to read and use SCM tags and commits

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

Michael Osipov closed MRELEASE-1078.
------------------------------------
    Resolution: Fixed

Fixed with [b899ace1b448a29aa7645aecc91b519673079e39|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=b899ace1b448a29aa7645aecc91b519673079e39].

> Support version policy to read and use SCM tags and commits
> -----------------------------------------------------------
>
>                 Key: MRELEASE-1078
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1078
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>            Reporter: Niels Basjes
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.0.0-M8
>
>
> My aim is to support having something like [https://www.conventionalcommits.org/] in the maven-release-plugin.
> This simply means that the next version of a release is calculated from the last tag in the version history and the patterns in the commit messages since that tag.
> This issue depends on https://issues.apache.org/jira/browse/SCM-977 being available (i.e. we have the commit messages and tags available).
> h4.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)