It's all about the answers!

Ask a question

Loading or fetching a workspace without project root folder


Brian Gillan (3215330) | asked Mar 12 '09, 5:27 p.m.
If I have a project structure such as this:
componentA:
projectAroot\.project
\subdir1
\subdir1_1
\projectAfile.txt
componentB:
projectBroot\.project
\subdir1
\sundir1_1
\projectBfile.txt

Is it possible during teamFetch (JBT) of load (scm tool) to create:
\.project (from projectAroot)
\subdir
\subdir1_1
\projectAfile.txt
\projectBfile.txt

Essentially giving me:
1. elimination of the root folder in each project
2. overlay of projectB's directory structure on top of projectA's
(because other than the root folder, they have the same directory
structure).

We're integrating RTC into our existing build environment, and if we
can't accomlish the above, we need to re-vamp build processing.

Thanks, Brian

7 answers



permanent link
Geoffrey Clemm (30.1k23035) | answered Mar 12 '09, 9:16 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Just for interest's sake, why aren't you laying out your projects in the
repository the same way you want them laid out on disk?

Cheers,
Geoff

Brian Gillan wrote:
If I have a project structure such as this:
componentA:
projectAroot\.project
\subdir1
\subdir1_1
\projectAfile.txt
componentB:
projectBroot\.project
\subdir1
\sundir1_1
\projectBfile.txt

Is it possible during teamFetch (JBT) of load (scm tool) to create:
\.project (from projectAroot)
\subdir
\subdir1_1
\projectAfile.txt
\projectBfile.txt

Essentially giving me:
1. elimination of the root folder in each project
2. overlay of projectB's directory structure on top of projectA's
(because other than the root folder, they have the same directory
structure).

We're integrating RTC into our existing build environment, and if we
can't accomlish the above, we need to re-vamp build processing.

Thanks, Brian

permanent link
Brian Gillan (3215330) | answered Mar 12 '09, 9:39 p.m.
Geoff, I'm not generally an Eclipse user... setting this up for another
group. I assumed that Eclipse requires a root folder in each project,
and when Team Shared, that's how it goes into RTC. Are you saying I can
put stuff into a component that will not have a root folder?

Thanks, Brian

permanent link
Geoffrey Clemm (30.1k23035) | answered Mar 13 '09, 1:55 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You can put any file system structure you want into a component, with or
without projects or project roots.

In RTC-1.0, there were some limitations in terms of how you can then
load that component into the file system. In RTC-2.0, those limitations
have been removed (in particular, the currently available beta of
RTC-2.0 no longer has these limitations).

So I'd recommend that you lay out your projects in your component
exactly how you want them laid out on disk when they are loaded.

Cheers,
Geoff



Brian Gillan wrote:
Geoff, I'm not generally an Eclipse user... setting this up for another
group. I assumed that Eclipse requires a root folder in each project,
and when Team Shared, that's how it goes into RTC. Are you saying I can
put stuff into a component that will not have a root folder?

Thanks, Brian

permanent link
Brian Gillan (3215330) | answered Mar 13 '09, 4:39 p.m.
Geoff, We're using RTC-1.0 (actually v1.0.1) and this is a production
environment, so I would be hesitant to move to RTC-2.0 beta.

Given we're using RTC-1.0, I don't see how to create the structure I
describe in Eclipse... doesn't an Eclipse project have to exist in a folder?

And, when I share an Eclipse project with RTC, I see no option to load
the component with just the content of the Eclipse project. It brings
along the project folder as well.

Are you saying I need to move to 2.0 to achieve what I want? Or am I
missing something in how I'm using Eclipse and sharing my project with RTC?

Thanks, Brian

permanent link
Geoffrey Clemm (30.1k23035) | answered Mar 14 '09, 10:49 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Brian,

Let's go back to your original question (in case I misunderstood what
you were trying to do):

Brian Gillan wrote:
If I have a project structure such as this:
componentA:
projectAroot\.project
\subdir1
\subdir1_1
\projectAfile.txt
componentB:
projectBroot\.project
\subdir1
\sundir1_1
\projectBfile.txt

Is it possible during teamFetch (JBT) of load (scm tool) to create:
\.project (from projectAroot)
\subdir
\subdir1_1
\projectAfile.txt
\projectBfile.txt

Why do you want to have a file from project B be loaded in project A?

Cheers,
Geoff


Brian Gillan wrote:
Geoff, We're using RTC-1.0 (actually v1.0.1) and this is a production
environment, so I would be hesitant to move to RTC-2.0 beta.

Given we're using RTC-1.0, I don't see how to create the structure I
describe in Eclipse... doesn't an Eclipse project have to exist in a
folder?

And, when I share an Eclipse project with RTC, I see no option to load
the component with just the content of the Eclipse project. It brings
along the project folder as well.

Are you saying I need to move to 2.0 to achieve what I want? Or am I
missing something in how I'm using Eclipse and sharing my project with RTC?

Thanks, Brian

permanent link
Brian Gillan (3215330) | answered Mar 16 '09, 1:20 p.m.
Geoff, This comes from how the projects we are looking to migrate from
PVCS have been structured in PVCS. There are a number of projects
currently managed in PVCS that share a common chunk (a dozen of so
files). In PVCS, this is done using a linking mechanism, much like a
symlink in UNIX. So for each project, the "common" files appear in the
same sub-folder structure within each project. We're trying to reproduce
this behavior in RTC/Eclipse.

Thanks, Brian

permanent link
Heather Fraser-Dube (4512) | answered Mar 24 '09, 10:15 a.m.
JAZZ DEVELOPER
Even with the new load features of 2.0 this is not possible.
We do not support the "nesting" or overlaying of shares on top of one
another.

- Heather
SCM committer

Brian Gillan wrote:
If I have a project structure such as this:
componentA:
projectAroot\.project
\subdir1
\subdir1_1
\projectAfile.txt
componentB:
projectBroot\.project
\subdir1
\sundir1_1
\projectBfile.txt

Is it possible during teamFetch (JBT) of load (scm tool) to create:
\.project (from projectAroot)
\subdir
\subdir1_1
\projectAfile.txt
\projectBfile.txt

Essentially giving me:
1. elimination of the root folder in each project
2. overlay of projectB's directory structure on top of projectA's
(because other than the root folder, they have the same directory
structure).

We're integrating RTC into our existing build environment, and if we
can't accomlish the above, we need to re-vamp build processing.

Thanks, Brian

Your answer


Register or to post your answer.