[ http://jira.codehaus.org/browse/MCHANGELOG-3?page=comments#action_62002 ] 

Julian Wood commented on MCHANGELOG-3:
--------------------------------------

Sorry guys - I've been swamped. I'll get to it tomorrow.

> Links in File Activity Report can be wrong when using subversion, after a 
> copy command has been issued
> ------------------------------------------------------------------------------------------------------
>
>          Key: MCHANGELOG-3
>          URL: http://jira.codehaus.org/browse/MCHANGELOG-3
>      Project: Maven 2.x Changelog Plugin
>         Type: Bug

>  Environment: OSX 10.4.3, java 1.4.2_09
>     Reporter: Julian Wood
>     Assignee: Edwin Punzalan
>     Priority: Minor
>      Fix For: 2.0
>  Attachments: MOJO-216-changelog-maven-plugin-1a.patch, 
> MOJO-216-changelog-maven-plugin.patch, changelog.xml, svnlog2.txt
>
>
> When you do a subversion copy command, the list of files produced by svn log 
> often have additional information that is part of the filename:
> R /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128)
> In SvnChangeLogParser.java, the file name is parsed as  
> /tags/prt-1.3/prt-admin/pom.xml (from /trunk/prt-admin/pom.xml:128) when of 
> course it should be /tags/prt-1.3/prt-admin/pom.xml. This is most 
> significantly manifested when a link is generated, such as in the File 
> Activity Report.
> http://...?repname=prt&sc=0&path=/tags/prt-1.3/pom.xml%20(from%20/trunk/pom.xml:128)
> I can see two approaches to the problem. The simplest is to add a regular 
> expression which deletes the extraneous data, but then you lose that 
> potentially valuable information. Maybe ChangeLogFile should keep track of a 
> file (path) and a name, rather than just a name, so that the link can be made 
> properly.

-- 
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

Reply via email to