[
http://jira.codehaus.org/browse/MCHANGES-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122815
]
Dennis Lundberg commented on MCHANGES-78:
-----------------------------------------
The other day, I had a look at the generated site that you attached to this
issue. When you first proposed this plugin on the dev-list I couldn't
understand how it would work and how it differed from maven-changelog-plugin. I
understand that better now.
To me it seems that the input and output of your plugin is somewhere in-between
maven-changes-plugin and maven-changelog-plugin. However I can't see a good way
to integrate it into either one. The changes plugin produces a report based on
an issue tracking system. Currently we support changes.xml file and JIRA as
issue trackers. Your approach of parsing the commit messages from an SCM
doesn't fit well into that. We have a saying where i live. It goes something
like this:
_"Don't cross the river to fetch water"_
That pretty much describes how I feel about your plugin. Why would you want to
ask the SCM about issues that are already tracked in an issue tracker? It seems
like an extra, and unnecessary, step. Just ask the issue tracker directly. You
are bound to get better texts to put in the report than you would by parsing
SCM messages.
> Build a changes report by parsing svn comments
> ----------------------------------------------
>
> Key: MCHANGES-78
> URL: http://jira.codehaus.org/browse/MCHANGES-78
> 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, svnchangelog-plugin-jdk1.4.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 tracker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
