|
From: SourceForge.net <no...@so...> - 2010-11-26 18:34:23
|
Bugs item #3119903, was opened at 2010-11-26 18:34 Message generated for change (Tracker Item Submitted) made by prmartinuk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=833326&aid=3119903&group_id=164845 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Input Layer: SVN Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Martin (prmartinuk) Assigned to: Nobody/Anonymous (nobody) Summary: Fails with SVN logs with full merge history Initial Comment: If you create the SVN logs with the full merge history ("-g" or "--use-merge-history") then StatSvn fails to parse the log file. The problem seems to be that the full merge history creates nested "logentrry" nodes which contain the history from the merging e.g. .... <logentry revision="999"> ... <msg>I merge in my changes from another branch</msg> <logentry revision="995"> ... <msg>A change I made on the other branch</msg> </logentry> <logentry revision="994"> ... <msg>A change I made on the other branch</msg> </logentry> </logentry> As a workaround you can comment out the fatalError(...) in net.sf.statsvn.input.SvnXmlLogFileHandler.checkLastElement(SvnXmlLogFileHandler.java:101). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=833326&aid=3119903&group_id=164845 |