Input dir. Directory where the files under SCM control are located.

Allows the user to choose which scm connection to use when connecting to the scm. Can either be "connection" or "developerConnection".

Used to specify the date format of the log entries that are retrieved from your SCM system.

Used to specify the absolute date (or list of dates) to start log entries from.

List of developers to be shown on the report.

A template string that is used to create the changeset URL. If not defined no change set link will be created.

There is one special token that you can use in your template:

• %REV% - this is the changeset revision

Example: http://fisheye.sourceforge.net/changelog/a-project/?cs=%REV%

Note: If you don't supply the %REV% token in your template, the revision will simply be appended to your template URL.

A template string that is used to create the URL to the file details. There is a special token that you can use in your template:

• %FILE% - this is the path to a file

Example: http://checkstyle.cvs.sourceforge.net/checkstyle%FILE%?view=markup

Note: If you don't supply the token in your template, the path of the file will simply be appended to your template URL.

A template string that is used to create the revision aware URL to the file details in a similar fashion to the displayFileDetailUrl. When a report contains both file and file revision information, as in the Change Log report, this template string can be used to create a revision aware URL to the file details.

If not defined this template string defaults to the same value as the displayFileDetailUrl and thus revision number aware links will not be used.

There are two special tokens that you can use in your template:

• %FILE% - this is the path to a file
• %REV% - this is the revision of the file

Example: http://fisheye.sourceforge.net/browse/a-project/%FILE%?r=%REV%

Note: If you don't supply the %FILE% token in your template, the path of the file will simply be appended to your template URL.

Encodes slashes in file uri. Required for some repository browsers like gitblit

List of files to include. Specified as fileset patterns of files to omit in the report

Used to specify the format to use for the dates in the headings of the report.

List of files to include. Specified as fileset patterns of files to include in the report

A pattern used to identify 'issue tracker' IDs such as those used by JIRA, Bugzilla and alike in the SCM commit messages. Any matched patterns are replaced with issueLinkUrl URL. The default value is a JIRA-style issue identification pattern.

Note: Default value is [a-zA-Z]{2,}-\d+

The issue tracker URL used when replacing any matched issueIDRegexPattern found in the SCM commit messages. The default is URL is the codehaus JIRA URL. If %ISSUE% is found in the URL it is replaced with the matched issue ID, otherwise the matched issue ID is appended to the URL.

If true, file and revision information is omitted for each SCM entry.

The file encoding when writing non-HTML reports.

Output file for xml document

Allows the user to make changelog regenerate the changelog.xml file for the specified time in minutes.

The passphrase (used by java svn).

The user password (used by svn and starteam protocol).

The private key (used by java svn).

List of provider implementations.

Used to specify the number of days of log entries to retrieve.

The URL to view the scm. Basis for external links from the generated report.

Skip the Changelog report generation. Most useful on the command line via "-Dchangelog.skip=true".

The system properties to use (needed by the perforce scm provider).

The url of tags base directory (used by svn protocol).

Used to specify the tag (or list of tags) to start log entries from.

Used to specify whether to build the log using range, tag or date.

The user name (used by svn and starteam protocol).