[
https://issues.apache.org/jira/browse/SCM-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961888#comment-17961888
]
ASF GitHub Bot commented on SCM-520:
------------------------------------
jira-importer commented on issue #733:
URL: https://github.com/apache/maven-scm/issues/733#issuecomment-2964615613
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
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 (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-api
> Affects Versions: 1.2
> Reporter: Johan Walles
> Priority: Major
>
> 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
(v8.20.10#820010)
