Using RTC with Cmd Line and External Editors
In our development environment most of our team works @ home, but remotely off of development machines in the lab for daily development. Due to the remote development we are using command line tools with the current source repository. We have noticed that you can use external editors like emacs, etc to modify the code in your workspace - however the tricky part is getting RTC to notice you have made changes. Once you make the change with the editor you could open RTC and do a refresh on the source tree and the change would be noticed..... Is there an equivalent way to do this with the command line?
2 answers
In our development environment most of our team works @ home, but remotely off of development machines in the lab for daily development. Due to the remote development we are using command line tools with the current source repository. We have noticed that you can use external editors like emacs, etc to modify the code in your workspace - however the tricky part is getting RTC to notice you have made changes. Once you make the change with the editor you could open RTC and do a refresh on the source tree and the change would be noticed..... Is there an equivalent way to do this with the command line?
Hi
You could try the commandline tools for RTC (and probably get emacs, etc to do the calls for you without having to dive back into RTC each time). Check the RTC client Help - search for commandline.
Alternatively, I have tried (while doing some performance testing) using a remote connection to a desktop machine running an RTC Eclipse client (on another continent). That worked well and seemed quite usable.
anthony
...Once you make the change with the editor you could open RTC and do a refresh on the source tree and the change would be noticed..... Is there an equivalent way to do this with the command line?
It sounds like you want to commit your changes to your remote workspaces. If that's the case, then you should run
$ scm checkin {files-and-folders-to-commit}
to copy your changes to your remote workspaces and then
$ scm deliver {change-sets-to-push}
to push your changes to the stream.
e