[JIRA] (JENKINS-14365) Wacky number for changes in build using Mercurial plugin

[jgl...@cloudbees.com (JIRA)]

jglick commented on JENKINS-14365 Wacky number for changes in build using Mercurial plugin To answer my own question: because SubversionChangeLogSet.LogEntry does define an public int getRevision() which is meaningful. Really it should have been the Subversion plugin which defined a custom project-changes.jelly with the special behavior of replacing list item numbers with Subversion revision numbers, a trick that of course is only meaningful for centralized SCMs which use integer revision numbers. The various fix options are: 1. Remove value="${c.revision}" in core, override project-changes.jelly in the Subversion plugin, and eventually remove the project-changes.jelly override in the Git plugin (and anywhere else this might have been worked around) perhaps once the core fix makes it into an LTS release. 2. Work around in the Mercurial plugin the same way as in the Git plugin, basically compounding the error. 3. Change core to use getRevision only if it returns an Integer, rather than a String as the Git or Mercurial plugins would.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira