How to Crosslink Source Files in RTC?
Consider a software development organization that has a software project A, whose file structure must include two files from a wholly independent software project B. Any time project B delivers a new version of either of these two dependent files to its parent stream, we want to automatically accept and copy that change into our project A. But, our developers in project A should not be able to edit those dependent files (they should appear as read-only).
AccuRev supports such situations with Crosslinks and Symbolic links (http://www.accurev.com/cross-links-symbolic-links.html). However, RTC does not seem to support this? Our team requires this feature -- please help!
AccuRev supports such situations with Crosslinks and Symbolic links (http://www.accurev.com/cross-links-symbolic-links.html). However, RTC does not seem to support this? Our team requires this feature -- please help!
One answer
RTC 2.0.0.2 (coming soon!) will support symbolic links.
Or you can try to use permissions to obtain a workflow that you want. See
http://jazz.net/library/article/215.
On Tue, 17 Nov 2009 16:37:57 -0500, brian.barritt
<brian> wrote:
Or you can try to use permissions to obtain a workflow that you want. See
http://jazz.net/library/article/215.
On Tue, 17 Nov 2009 16:37:57 -0500, brian.barritt
<brian> wrote:
Consider a software development organization that has a software
project A, whose file structure must include two files from a wholly
independent software project B. Any time project B delivers a new
version of either of these two dependent files to its parent stream,
we want to automatically accept and copy that change into our project
A. But, our developers in project A should not be able to edit those
dependent files (they should appear as read-only).
AccuRev supports such situations with Crosslinks and Symbolic links
(http://www.accurev.com/cross-links-symbolic-links.html). However,
RTC does not seem to support this? Our team requires this feature --
please help!