maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] Commented: (MCHANGES-78) Build a changes report by parsing svn comments
Date Fri, 08 Feb 2008 16:36:28 GMT


Dennis Lundberg commented on MCHANGES-78:

Thanks to Emmanuel and Rémy for your feedback.

I agree when you say the this issue has not been handled well from our side. First we should
assess whether or not the idea of the submission is good or bad. If we like it, then we can
make suggestions or demands on packaging, code style, licensing and such issues. Sorry about
that. We'll try to do better in the future.

The changes.xml file for me is a "poor mans issue tracker". Dead simple to use for anyone,
even those that don't even have an SCM to store their source code.

Judging by your comments I must have misunderstood how the plugin works. Are you saying that
it can be used *without* an issue tracker?

Have you guys looked at maven-changelog plugin? It fetches the commit message from your SCM
and produces  a report of every commit made. See for example:

Perhaps we could integrate your Commit Message Parser into that plugin instead? Thereby being
able to mark the commits by type; add, fix etc.

> Build a changes report by parsing svn comments
> ----------------------------------------------
>                 Key: MCHANGES-78
>                 URL:
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Improvement
>            Reporter: Emmanuel Hugonnet
>            Priority: Minor
>         Attachments: site.tar.gz, svn-changelog-plugin-jdk1.4.tar.gz, svn-changelog-plugin.tar.gz,
> Builds a changes report by parsing svn comments.
> You can configure this plugin as any reporting plugin. But it has specific configuration
parameters :
>     * grammar : this allows you to specify the grammar used to parse the svn logs.
>       Currently it supports two grammars :
>           o "MANU" which uses @operation:issue;
>           o "REMY" with [operation:issue]
>     * trackerType : this allows you to specify the issue tracker used.
>       Currently it supports two trackers :
>           o codex
>           o jira
>     * trackerUrlPattern : this allows you to specify a pattern to link an issue to any

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message