LLuna
StaffJoined 11 years ago
User Profile
Staff
User Widgets
Contributions
Re: Code Collaborator plugin in Eclipse 3.6.2
Hi, There is a known issue with trying to use any eclipse plugin version (except 7237), against server version 7237. Could this be the case you guys are running into? If not, can you send us a debug log so we can take a look? To create a debugging log, please go to Window > Preferences > Code Collaborator > Capture Debugging Log. This will open a Debugging window. With that window still open, please reproduce the issue and press "Save Log." To get the configuration information, go to "Help" -> "About ..." -> "Installation Details" -> "Configuration" tab. Select all of the text in the "Configuration Details" box and save it in a file. Then click "View Error log" and save that information in a file as well. Send those files to our support email (codecollab@smartbear.com) and we'll take a look. Thanks, Luis Luna2KViews0likes0CommentsRe: Error happened when opening an action item in eclipse
Hi, We currently have an issue with our 7.2.7327 client trying to connect to any other version that is not 7237. To resolve this, you can upgrade your server to 7237, or you can rollback your eclipse client to a previous version. Thanks, Luis Luna SmartBear Technical Support.707Views0likes0CommentsRe: P4Sandbox support
Hi, We don't have specific support for P4Sandbox yet planned, but from reports from other users I believe you can workaround by setting yout --p4port option to point where the sandbox server is running. We don't support loopback addresses, so you would have to specify your box IP adress instead (e.g. 192.168.0.34:1666 instead of localhost:1666). Let us know if you have additional questions, Luis Luna SmartBear Technical Support.670Views0likes0CommentsRe: Path of the file uploaded in the server (for static analysis)
Hi, To answer your question, you can find this path using the md5 of the file that you just uploaded. One way to retrieve the md5 from code collaborator is using the review-xml command, with the --xpath //artifact option to just retrieve the uploaded artifacts for the review: ccollab admin review-xml <review-id> --xpath //artifact You will get an output like this: <artifact changelistId="1" changelistScmId="" lines="644" lines-added="11" lines-changed="0" lines-deleted="0" versionId="10"> <path>path/to/file/in/review</path> <md5sum>21c25ec1efd7fb9f1e24168cdaf55e05</md5sum> <change-type>M</change-type> <scmVersion>c7a568c</scmVersion> <scm config-a="diffs" config-b="scm-system" id="3" type="none"/> <prev-path>prev/path/to/file/in/review</prev-path> <prev-md5sum>b100599b9c4aa8e3ecb5ab8e6e514b6e</prev-md5sum> <prev-change-type>M</prev-change-type> <prev-scmVersion>a7a0bb6</prev-scmVersion> <num-comments>0</num-comments> <num-defects>0</num-defects> </artifact> Then you can use the md5sum matching the original file path (in <path>) to locate the file in your file system. You will need to use a command line tool in order to find it (such as find in linux, or dir in Windows), as it might be under several subdirectories. But, if you really want the file content you can simply use the versionId and call: ccollab admin wget /data/server?versionid=<version id> In the example above you can do ccollab admin wget /data/server?versionid=10 And that should retrieve the contents of that file. These commands are described here: http://support.smartbear.com/viewarticle/25602/ Let us know if you have additional questions, Luis Luna SmartBear Software Technical Support1.1KViews0likes0Comments