Alternatives to manually refreshing sandbox
![]()
Hi!
Since I'm not using Eclipse to edit my sources, it doesn't track changes to my sandbox. This leads to me having to refresh the sandbox manually to update the pending changes view. This wouldn't be that bad if my sandbox didn't contain two humungous libraries (which I'm not modifying but only using) and a small set of files that form a program, which is what I'm actually working on. Since refreshing the sandbox looks at all components, doing so takes a painfully long time. Now, of course I'm aware that I can select the "Refresh Sandbox ..." option to restrict the parts that are scanned, skipping the rarely-modified parts. What would be a real improvement there is if the choice there was remembered, because usually the parts to refresh are the same as those refreshed last time. Should I write an enhancement request for that? Further, what I'm wondering is if there isn't any filesystem monitor that can detect changes to the sandbox and accordingly notify RTC that there are pending changes. I'd need such a (nonportable) monitor for a win32 system specifically. Also, how do other people handle or avoid this issue? Uli |
3 answers
![]()
This story item seems to be what you're asking for: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=169741
You may also want to open an enhancement to remember the selection with the "Refresh Sandbox..." action. |
![]()
Thanks for the link, Tim! The enhancement request is filed as https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=177973
Uli |
![]()
Just found another thing I can do: Since the huge and static component is compiled once and then installed outside the directory where it is loaded by RTC, I can simply compile and install it and then unload the otherwise unused component. Only disadvantage is that if I need to debug into it, I don't have the sources, but that shouldn't happen anyway.
Cheers! Uli |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.