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 2015/09/06 22:46:29 UTC

[jira] [Closed] (SCM-520) Please add support for change numbers

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

Michael Osipov closed SCM-520.
------------------------------
    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 applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Please add support for change numbers
> -------------------------------------
>
>                 Key: SCM-520
>                 URL: https://issues.apache.org/jira/browse/SCM-520
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-api
>    Affects Versions: 1.2
>            Reporter: Johan Walles
>
> Please add support for retrieving change numbers to the SCM API.
> Currently there's an ugly SVN-specific hack here:
> http://mojo.codehaus.org/buildnumber-maven-plugin/
> Since most SCM systems support the concept of build numbers it should be in the API.  And the buildnumber plugins shouldn't have to be SVN specific.



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