Hi

I've been looking at different solutions for MCHANGELOG-16 [1] and have come to the conclusion that we need more ways to configure the plugin.

1. As more and more applications are developed that present the contents of an SCM repository on the web, we are facing problems configuring links to them. I refer to systems like ViewVC and will call them SCM front-ends from here on, in lack of a better description.

In the issue at hand we have a front-end to a Subversion repository. It might be possible to squeeze this into the current code base, but eventually the code will turn into spaghetti.

I propose that we introduce a new configuration parameter "scmFrontEnd" which will be a String, like "viewvc" or "websvn". If no scmFrontEnd is configured we will use a default one. The defaults will pretty much be the current code in the plugin. If one is configured we will create links to the front-end in special ways for each one. This will work similarly to how we handle Issue management systems.

Some backwards-incompatible changes will have to be made and decisions on default front-ends need to be made.

2. To handle other systems we need additional parameters. We should replace the current "displayFileDetailUrl" with two new parameters; one that links to a file and one that links to a version of a file. These will be templates with two special tokens %FILE% and %REVISION% in the same way that the changes plugin does [2]. By doing this we can ensure that the user is always able to configure their own front-end, if that front-end is not directly supported by the changelog plugin.


[1] http://jira.codehaus.org/browse/MCHANGELOG-16
[2] http://maven.apache.org/plugins/maven-changes-plugin/changes-report-mojo.html#issueLinkTemplate

--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to