Well, we only support Subversion and Mercurial currently. We need a BetterChangeSet for each SCM that is not provided by Maven SCM.
To support another scm should be quite easy, it involves modifying the maven scm command and maven scm consumer to get a list of BetterChangeSet instead of a list of ChangeSet.
We support JIRA, Bugzilla, and SourceForge trackers. But since we use a trackerUrlPattern you could well set another tracker with its url writing :
<trackerUrlPattern>my_tracker_url?bugIdParam={0}</trackerUrlPattern>
<trackerUrlPattern>#</trackerUrlPattern>
We wanted a changelog report like the one produced by the maven-changes-plugin but we thought that it is better (and DRYer) to generate the reports from the scm comments rather than a changes.xml file.
We tried our best in order to improve the maven-changes-plugin by adding a new goal, but unfortunately this was rejected (cf. MCHANGES-78 and maven2 jira plugin?).
So we decided to create this plugin (cf. MOJO-1026).
The maven-changelog-plugin generates reports regarding the recent changes in the SCM.
The scm-changelog-plugin is used to display the changes that have occured between different releases of a project while the maven-changelog-plugin reports each revision of the project.