Is there a difference between the eclipse workspace and the sandbox for RTC?
3 answers
IMO it's very unfortunate that RTC decided to overload the term workspace with a different meaning than was already understood in Eclipse.
Comments
Thanks Jeff, that is what I thought looking at the structure as well.
1 vote
Glad to help. Please to sure to accept the answer as the correct one :)
1 vote
Despite the downvote & clarification from Geoff Clemm, the absolute most common usage that I've ever encountered is for there to be only one RTC sandbox associated with an Eclipse workspace, where the RTC sandbox and Eclipse workspace are co-located.
1 vote
I agree that is common usage for Eclipse users (and one I personally recommend for Eclipse users in all but a few special cases), but saying it this way would be confusing for users that need to deal with those special cases, and can be very confusing for non-Eclipse users, who might interpret this as saying they need to have an Eclipse workspace in order to load files onto disk.
An RTC sandbox is a host system directory with a .jazz5 directory in it.
So a given host system directory can be just an Eclipse workspace, just an RTC sandbox, both, or neither.
By default, the RTC Eclipse plug-in will make your initial RTC sandbox be the same directory as the Eclipse workspace, so the default RTC sandbox used from within Eclipse will be the Eclipse workspace. But that is just the default behavior. You can have multiple sandboxes associated with an Eclipse workspace (one of which can be the Eclipse workspace itself, but that is not required). You can even have the same sandbox associated with multiple Eclipse workspaces (but that is usually to be avoided, for many reasons).
To view and manipulate the RTC sandboxes associated with a given Eclipse workspace, use the "sandboxes" Eclipse preference.
