Creating a load rule in the project explorer the component is not linked to a workspace
I created a new load rule. All but three of the components could be loaded as is, however three of the components I had to load as because I had to change the paths of the components. The three components that I changed the path on show up in project explorer, but the component is not connected to the workspace. Why is that?
One answer
The pathname you specify via "load as" (prior to 6.0) causes the creation of non-version-controlled folders in your sandbox, which therefore will not be associated with any component. For example, if you load folder "foo" at pathname "x\y\z", then when you load folder "foo", the non-version-controlled folders "<sandbox-root>\x", "<sandbox-root>\x\y", and "<sandbox-root>\x\y\" will be created, and the "foo" will be loaded at "<sandbox-root>\x\y\z\foo". And when you "unload" the component, those non-version-controlled folders are left in place in the sandbox (so you'll have to delete them manually if you want to get rid of them). As I recall, the "2 loaded" annotation on a folder means that there are two folders/files "loaded" into that folder (or something like that :-).
Note that starting in V6.0, "nested loading" is supported, and you are allowed to use "load as" to load a component under a version-controlled directory in another component.
As for the empty bin directory ... if there is no empty bin directory in the repository, then that must have been created by Eclipse, and not by RTC.
Note that starting in V6.0, "nested loading" is supported, and you are allowed to use "load as" to load a component under a version-controlled directory in another component.
As for the empty bin directory ... if there is no empty bin directory in the repository, then that must have been created by Eclipse, and not by RTC.
Comments
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jun 05 '15, 3:47 p.m.nannette Mori
Jun 05 '15, 4:19 p.m.