Contributions
Re: Collaborator 8 + Git. Adding commits?
Hello, There are a few options... Probably the best way right now is to use "Add Git Diffs..." instead of "Add Commits...". This will allow you to specify an arbitrary Git diffspec and add all the changes in there as one changelist. However it's not quite as nice as adding each commit as a separate changelist because you can't see the commit comments. Another option is to list multple Git commits at once. Simply enter multiple commit hashes in to the box, separated by commas. You might want to automate this using our command-line tool - "Add Commits..." in the GUI is equivalent to our command-line "ccollab addchangelist" command. Note on the command-line you separate commit hashes with a space, not with commas. Unfortunately none of those options is ideal. I would like to see us add a feature that let you specify a range of commits using the standard Git syntax and then we automatically add each commit in the range as we do when you use "Add Commits..." in the GUI. If that sounds good to you please vote for it on our feedback forum here:http://feedback.codecollab.com/forums/4652-code-collaborator-features/suggestions/2924333 Regards, Roy2.6KViews0likes0CommentsRe: Can CVS diff type review be done through Eclipse plug-in?
Hello Charles, That's right, that feature is not available in our Eclipse plugin yet. If this feature is important to you please vote for it on our feature requrest site:http://feedback.codecollab.com/forums/4652-code-collaborator-features/suggestions/277585-upload-arbitrary-cvs-diffs-from-eclipse-plugin In the meantime you can add CVS diffs using our standalone GUI client or command-line client. Regards, Roy624Views0likes0CommentsRe: unable to open Code collaborator page in browser
Hello, You appear to have multiple XML files in your <install>/tomcat/conf/Catalina/localhost directory. This is a problem - there MUST be only one XML file in that directory, named "ROOT.xml". You can have other files in there (e.g. backups of the ROOT.xml file) but you have to name them something that doesn't end in ".xml". To fix the problem first shut down your server, then go in to that directory and move/delete/rename the other files so that "ROOT.xml" is the only "*.xml" file. Then restart your server. Regards, Roy2.4KViews0likes0CommentsRe: Attaching SVN changelists from command line
We do our best to auto-detect the SCM information from the command-line. In the case of SVN we check if there is an "svn" executable on the PATH and then run "svn info" in the current working directory. If the current working directory is a Subversion working copy then we can get the info we need from that. If auto-detect doesn't work for whatever reason then you can configure us with the information we need using "global options". Global options can be specified with switches on each command-line invocation or you can save them using the "ccollab set" command. See here in our manual for more info:http://support.smartbear.com/viewarticle/25511/#configuration Regards, Roy603Views0likes0CommentsRe: Creating a Review with web services
Hello Scott, I'm sorry, this functionality does not exist in our web services API yet. You're going to have to script our command-line client instead. Seehttp://support.smartbear.com/viewarticle/25602/and particularlyhttp://support.smartbear.com/viewarticle/25563/ Regards, Roy1.1KViews0likes0CommentsRe: Intermittent issue with commandline client hanging
We warn in the log when users fail authentication, e.g. because they supplied the wrong password - it' s just a warning and if users aren't complaining then you can probably ignore it. Since you just switched from Active Directory authentication to our built-in authentication I am not surprised you're seeing these. Probably your users are automatically typing in their Active Directory passwords, and then when that doesn't work they realize they need to set up a new password in our built-in auth scheme.1.9KViews0likes0Comments