(1) Yes, you can now load any tree of from the repository workspace to
any location on disk.

(2) I don't know how to do this directly, but you can achieve this by:
- loading into the file system the parent folder (say, "p") into which
you want it to be shared
- moving the folder you want to share under where you loaded "p"
- checkin that folder
- unload "p"
- load your newly shared folder back to its original location

(3) It doesn't look like you can do this directly, but you should be
able to use the same technique described for (2) to achieve the same
effect.

Cheers,
Geoff

David Ward wrote:
I've been playing with the new SCM features of 2.0beta1 and I some
questions arise.

1) Am I correct that 2.0 allows workspace components to be 'loaded'
anywhere in the filesystem i.e. not necessarily within the Eclipse
workspace.

It appears to me that the new 2.0 SCM features allow an existing
repository component be loaded pretty much anywhere.

2) Can an arbitrary filesystem directory be 'shared' ??

I couldn't see a way to do that.

3) When sharing an Eclipse project for the first time, must the
Eclipse project's root folder appear in the component ? or can I
share everything below the Eclipse project's root folder ?

Not sure if I explained that clearly :-)

Cheers

(1) Yes, you can now load any tree of from the repository workspace to
any location on disk.

(2) I don't know how to do this directly, but you can achieve this by:
- loading into the file system the parent folder (say, "p") into which
you want it to be shared
- moving the folder you want to share under where you loaded "p"
- checkin that folder
- unload "p"
- load your newly shared folder back to its original location

(3) It doesn't look like you can do this directly, but you should be
able to use the same technique described for (2) to achieve the same
effect.

Cheers,
Geoff

David Ward wrote:
I've been playing with the new SCM features of 2.0beta1 and I some
questions arise.

1) Am I correct that 2.0 allows workspace components to be 'loaded'
anywhere in the filesystem i.e. not necessarily within the Eclipse
workspace.

It appears to me that the new 2.0 SCM features allow an existing
repository component be loaded pretty much anywhere.

2) Can an arbitrary filesystem directory be 'shared' ??

I couldn't see a way to do that.

3) When sharing an Eclipse project for the first time, must the
Eclipse project's root folder appear in the component ? or can I
share everything below the Eclipse project's root folder ?

Not sure if I explained that clearly :-)

Cheers

Thanks Dave

Regarding 2) and 3) In Eclipse, we haven't enabled sharing from
directories below the project. I am not sure if the CLI supports it or
not. Raise us a work item explaining your usecase if it is necessary.
In the interim, you can use the workaround suggested.

In the load wizard, you can navigate down the tree and choose the
folders you want loaded into your sandbox. So it is not necessary to
load the top level folders under the component (you could do this in 1.0
even). In 2.0 you can now load those nested folders under folders that
are not at the root of the sandbox.

For example:
Component1
P
subdir1
subdir2
a.txt

You can load subdir2 under sandbox /mySandbox at
/mySandbox/dirNotUnderSrcCtl/anotherDirNUSC/subdir2

You can also load subdir2 as another name for example:
/mySandbox/dirNotUnderSrcCtl/anotherDirNUSC/alternateNameSubdir2

For these special types of loads, you need to use the load as menu
option from the repository files view. It allows you to specify a
relative path within the sandbox to load things at.

For more help, take a look at
https://jazz.net/wiki/bin/view/Main/SCMFlexibleLoading

- Heather
SCM committer

David Ward wrote:
Thanks Geoff

2.0 certainly has some nice SCM features. My team is going to like it.

Regarding 3) Root Folders

Before posting my question I hadn't noticed "Loading or fetching a
workspace without project root folder" and the answers there.

I'm not looking to 'overlay' files the way the author of that post
wanted to do, but I would like to not be forced to see the component
root folder in the loaded filesystem sandbox.

Your answer to that post suggests that 2.0 can do this ?
Have I misunderstood ?

Dave


Geoffrey Clemm wrote:
(1) Yes, you can now load any tree of from the repository workspace
to any location on disk.

(2) I don't know how to do this directly, but you can achieve this by:
- loading into the file system the parent folder (say, "p") into
which you want it to be shared
- moving the folder you want to share under where you loaded "p"
- checkin that folder
- unload "p"
- load your newly shared folder back to its original location

(3) It doesn't look like you can do this directly, but you should be
able to use the same technique described for (2) to achieve the same
effect.

Cheers,
Geoff

David Ward wrote:
I've been playing with the new SCM features of 2.0beta1 and I some
questions arise.

1) Am I correct that 2.0 allows workspace components to be 'loaded'
anywhere in the filesystem i.e. not necessarily within the Eclipse
workspace.

It appears to me that the new 2.0 SCM features allow an existing
repository component be loaded pretty much anywhere.

2) Can an arbitrary filesystem directory be 'shared' ??

I couldn't see a way to do that.

3) When sharing an Eclipse project for the first time, must the
Eclipse project's root folder appear in the component ? or can I
share everything below the Eclipse project's root folder ?

Not sure if I explained that clearly :-)

Cheers