You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/03/09 19:05:13 UTC

[jira] Commented: (MPCHANGELOG-60) maven-changelog-plugin major rewrite

     [ http://jira.codehaus.org/browse/MPCHANGELOG-60?page=comments#action_30623 ]
     
Brett Porter commented on MPCHANGELOG-60:
-----------------------------------------

Thanks Henning. Please be patient for us to look at this as it is a significant patch.

If you intend to do major plugin rewrites, please talk to the Maven Dev List first. We have some code that addresses these issues slated to go into changelog in the future which you could have worked with.

> maven-changelog-plugin major rewrite
> ------------------------------------
>
>          Key: MPCHANGELOG-60
>          URL: http://jira.codehaus.org/browse/MPCHANGELOG-60
>      Project: maven-changelog-plugin
>         Type: Improvement
>     Reporter: Henning Schmiedehausen
>  Attachments: changelog.patch
>
> Original Estimate: 2 hours
>         Remaining: 2 hours
>
> This is a major rewrite of the maven-changelog-plugin to start tacking the abysmal state that it is in.
> I was pretty p*ssed to find out that I have to set a "factory" property when I want to use SVN, that the SVN support only works when the plugin runs in the correct working directory and that the date limitation does not work at all (at least on Linux).
> Also the different repository syntax from CVS (why do we have this scm:<scm type>:<scm subtype>:<host>:<repo>:<path> definition if no one cares about it?) is misleading, local URLs like file: or svn+ssh don't seem to work and all in all the whole SVN support is rudimentary at best. 
> This rewrite tackles the following problems:
> - Auto select the SCM type. Look at the second field and choose cvs, clearcase, perforce, starteam, svn.
> - do some code cleanup. Juggle a few constants, move a bit of the init code, make token parsing saner.
> - bring the SVN code somehow in line with CVS. Repository connections now look like CVS connection:
>    <repository>scm:svn:http:svn.apache.org:/repos/asf/foo/trunk</repository>
>    or 
>    <repository>scm:svn:svnssh:henning@svnserver.foo.org:/repos/local/opensource/foo</repository>
> - support for all SVN connection types (http, https, file, local, svn, svnssh)
> - support for passwords (when using the ";" delimiter):
>    <repository>scm;svn;http;henning:secret@svn.private.org;/repos/asf/foo/trunk</repository>
> - make the svn log actually look at the pom defined repository and not at "current working directory"
> - supply username and password to svn if given by the pom
> This patch should probably _not_ be applied "as is". It is a patch from our internal SVN to the current SVN head @ apache.
> It contains a few changes to e.g. project.xml which shouldn't be applied to the repo (but I'm much too lazy to start sorting out this patch). 
> If you give me karma for the changelog-plugin I'd even be willing to apply them to the Apache SVN myself. :-) 

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org