SVN import failed as a result of file merging
Since Collaborator uses the Subversion command-line client and its native commands to fetch the data from the local SVN repository or the SVN server, Collaborator will abort the entire uploading process if at least one of the outputs of the native commands will be unexpected or contain an error. This is done to prevent losing data or uploading the incorrect files to the Collaborator server. It would be good if CodeCollaborator would be able to handle importing a review from which a file has been removed during a merge to handle this differently. i.e:continue to import the files it could parse, and maybe put up a warning or something, rather than aborting the import.
Why are the wrong files uploaded when reviewing code on a subversion branch?
I changed one file on a sub-version branch. There are two total commits on the branch. I started a review by selecting both commits from a Tortoise SVN show log window. It took about 10 minutes for collaborator to make the review because it's including every single file in my project that I did not change. Starting a review on the very last commit works okay, and only one file is shown. However, starting a review with the initial commit on the branch results in my entire project being put under review. Has anyone ever seen anything like that? If so how do I fix it? I've observed this with Collaborator v11.0.11000 Manual. EDIT: If I merge to trunk, the reviews that I create from the commit log of the trunk work as expected and only the one changed file is added to the review. Tortoise SVN shows me the correct diff when showing the log when the branch is checked out. I'm not sure how exactly the integration works between SVN and collaborator but I would expect that it is better to review changes on a branch instead of having to merge first.