maven-issues mailing list archives

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


Emmanuel Hugonnet commented on MCHANGES-78:

Well we use the issue tracker as in the changes.xml, just to link to the issue. You must define
a tracker type with a tracker url (the typ is used for a regexp to put the bug id in the url)
.  So if you define a tracker url of '# ' it will work without a bug tracker. Also the id
is not mandatory so this way you won't need a tracker.  I was in the process of providing
a NoneTracker implementation to simplify this, as well as a support for Mercurial.
We keep only the messages which respect the grammar, dismissing the others. The changelog
team considered this to be closer to the changes plugin that is why I posted there, but of
course if it appears to be  more convenient with the changelog plugin I won't object ;o)
The code on codehaus is more recent with full site generated, better documentation (or so
I hope) and a good example of configuration.

> 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