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 07:16:30 GMT


Emmanuel Hugonnet commented on MCHANGES-78:

Thank you Dennis, this is a constructive remark :o)
I agree with you that why I contacted both teams.
The changes.xml is maintained by hand and I think that is far easier as a developer to add
more comments to my scm commit than to edit afterwards an xml file to add an entry and then
commit it.
If your opinion is "Just ask the issue tracker directly" then why does the changes plugin
exist ? Isn't it its goal to provide such a report ? (By the way I notice that most of the
teams use JIRA report when they release a new version and not the changes-plugin). 
I agree, an improvement would be to fetch the issue comments in the tracker ( version 2.0
? ) .
I accept your opinion, even if I have 3 teams using it here ;o) (maybe because we don't have
But why people asked for modifications (like jdk version, scm-api,package, ...) instead of
just stating the fact that they don't think it's a good idea ?

> 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