Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1
-
Fix Version/s: 2.2
-
Labels:None
-
Number of attachments :
Description
This is different a file revision, depending on the SCM being used. For instance if the user is using SVN then the changeset, which is identified by the revision number, contains all the files that were committed as part of that check-in. Tools such as FishEye and like let you browse changesets as well as specific files so my suggestion is to provide a new option that works in a similar fashion to the displayFileDetailUrl, called displayChangeSetDetailUrl.
/**
* A template string that is used to create the changeset URL.
*
* If not defined not change set link will be created
*
* There is one special tokens that you can use in your template:
* <ul>
* <li><code>%REV%</code> - this is the changset revision</li>
* </ul>
* <p>
* Example:
* <code>http://fisheye.sourceforge.net/changelog/a-project/?cs=%REV%</code>
* </p>
* <p>
* <strong>Note:</strong> If you don't supply the %REV% token in your template,
* the revision will simply be appended to your template URL.
* </p>
*
* @parameter expression="${displayChangeSetDetailUrl}"
*/
protected String displayChangeSetDetailUrl;
Patch to follow
