MantisBT - CMake
View Issue Details
0008128CMakeCTestpublic2008-11-20 09:422009-02-13 16:31
simonh 
Brad King 
normalmajoralways
closedduplicate 
 
 
0008128: ctest cannot handle SVN usernames with spaces
My users have spaces between First and Last names. This works fine for SVN (via client certificates or HTTP user names), but confuses CTest's parsing of "svn status".

svn_status_line_regex assumes that the output of "svn status --verbose" has no spaces in the user name. Would it be possible to use "svn status --xml --verbose" and parse the output as cmCTestUpdateHandlerSVNXMLParser already does for log messages?
No tags attached.
has duplicate 0008168closed Brad King CTest retrieval of file versioning history has logic errors 
child of 0010484closed Brad King There is no way to run svn/git/hg with custom options like --username. 
Issue History
2008-11-20 09:42simonhNew Issue
2008-11-24 09:51simonhNote Added: 0014164
2008-11-24 09:52simonhNote Edited: 0014164
2008-11-24 09:52simonhNote Edited: 0014164
2009-01-29 14:37Bill HoffmanStatusnew => assigned
2009-01-29 14:37Bill HoffmanAssigned To => Brad King
2009-01-29 14:42Brad KingNote Added: 0014724
2009-02-13 16:30Brad KingRelationship addedhas duplicate 0008168
2009-02-13 16:31Brad KingNote Added: 0014933
2009-02-13 16:31Brad KingStatusassigned => closed
2009-02-13 16:31Brad KingResolutionopen => duplicate
2011-01-17 15:57Brad KingRelationship addedchild of 0010484

Notes
(0014164)
simonh   
2008-11-24 09:51   
(edited on: 2008-11-24 09:52)
There are some fundamental issues with cmCTestUpdateHandler.cxx that I don't understand, such as the "modifiedOrConflict" flag which seems to be buggy to me.

I'm having difficulty writing a patch without knowing more about the code.

Please see my mailing list post:
http://www.cmake.org/pipermail/cmake/2008-November/025500.html [^]

(0014724)
Brad King   
2009-01-29 14:42   
I'm currently refactoring cmCTestUpdateHandler to get rid of the monolithic function and make it possible to support more VCS tools. I'll look at fixing this after the refactoring is complete.
(0014933)
Brad King   
2009-02-13 16:31   
Issue 0008168 more completely describes the issues, so I'm closing this version.