Hi,

in the past I had situations where RTC and other tools (ToolX below) would not run in the same Eclipse.

A strategy that did work was:

1. Create initial projects with ToolX
2. Import (copy) the projects into an RTC sandbox/workspace
3. Share the projects in RTC
4. Import the shared projects - no copy, just reference - back into ToolX

Afterwards it is possible to develop with ToolX. and create/modify files in the referenced Eclipse project.
From time to time switch to RTC and refresh the projects. RTC will show pending changes. Check in changes and deliver.

Ralph

Our team uses Eclipse (version 3.2.2) TPM development environment. RTC eclipse plugin is available for eclipse version 3.3.2 and above (going to 3.5) for RTC version 2.0.0.2.

We need to start using RTC repository.

How do we check in TPM code/artifacts given that it would not be possible to use the TPM eclipse IDE to talk to RTE due to eclipse version mismatch?

Options:
1. Use the web UI to create folders and check in files which belong to the TPM artifacts. Don't need to install any client for this.

2. Install RAD 7.5.x and RTC plugin on desktop. Create a general project and create folders linked to the TPM artifacts created by Eclipse 3.2.2. Check in files from within the RAD 7.5.x workspace using the RTC plugin support. In this case the user needs to install another Eclipse instance and the RTC plugin on his desktop.

Has anyone tried working with TPM dev environment, to check in code/artifacts into RTC repository?

What would be the best option?

Hi Ralph,

Just for interest's sake, what problems did you run into if in step 2,
you imported the ToolX projects into RTC via reference, rather than
copy? In particular, this would allow you to skip step 4.

Cheers,
Geoff

On 6/25/2010 7:23 AM, rschoon wrote:

Hi,

in the past I had situations where RTC and other tools (ToolX below)
would not run in the same Eclipse.

A strategy that did work was:

1. Create initial projects with ToolX
2. Import (copy) the projects into an RTC sandbox/workspace
3. Share the projects in RTC
4. Import the shared projects - no copy, just reference - back into
ToolX

Afterwards it is possible to develop with ToolX. and create/modify
files in the referenced Eclipse project.
From time to time switch to RTC and refresh the projects. RTC will
show pending changes. Check in changes and deliver.

Ralph

gajjarpswrote:
Our team uses Eclipse (version 3.2.2) TPM development environment.
RTC eclipse plugin is available for eclipse version 3.3.2 and above
(going to 3.5) for RTC version 2.0.0.2.

We need to start using RTC repository.

How do we check in TPM code/artifacts given that it would not be
possible to use the TPM eclipse IDE to talk to RTE due to eclipse
version mismatch?

Options:
1. Use the web UI to create folders and check in files which belong
to the TPM artifacts. Don't need to install any client for this.

2. Install RAD 7.5.x and RTC plugin on desktop. Create a general
project and create folders linked to the TPM artifacts created by
Eclipse 3.2.2. Check in files from within the RAD 7.5.x workspace
using the RTC plugin support. In this case the user needs to install
another Eclipse instance and the RTC plugin on his desktop.

Has anyone tried working with TPM dev environment, to check in
code/artifacts into RTC repository?

What would be the best option?

When I said "import the ToolX projects into RTC via reference", I meant
use "File -> Import -> General:Existing_Projects_into_Workspace" to
point Eclipse at the folders where the files already exist.

Cheers,
Geoff

On 10/8/2010 1:53 PM, gajjarps wrote:

Geoff:
Instead of copying files into a folder within Eclipse, I create a
folder that was linked to the folder on my desktop, which contained
files I wanted to check into RTC.
I am able to work with the files within Eclipse. However, eclipse/RTC
does not allow me to check in the linked files.
If I look at the file property - under source control, it clearly
states:

Ignored Due to: Linked resources are
ignored

Is there any way to make eclipse/RTC not ignore files which are linked
or are contained in linked folders?
Your help will be appreciated. Thank You.
..Pradeep

gmclemmwrote:
Hi Ralph,

Just for interest's sake, what problems did you run into if in step
2,
you imported the ToolX projects into RTC via reference, rather than

copy? In particular, this would allow you to skip step 4.

Cheers,
Geoff

On 6/25/2010 7:23 AM, rschoon wrote:
Hi,

in the past I had situations where RTC and other tools (ToolX
below)
would not run in the same Eclipse.

A strategy that did work was:

1. Create initial projects with ToolX
2. Import (copy) the projects into an RTC sandbox/workspace
3. Share the projects in RTC
4. Import the shared projects - no copy, just reference - back into
ToolX

Afterwards it is possible to develop with ToolX. and create/modify
files in the referenced Eclipse project.
From time to time switch to RTC and refresh the projects. RTC will
show pending changes. Check in changes and deliver.

Ralph

gajjarpswrote:
Our team uses Eclipse (version 3.2.2) TPM development environment.
RTC eclipse plugin is available for eclipse version 3.3.2 and above
(going to 3.5) for RTC version 2.0.0.2.

We need to start using RTC repository.

How do we check in TPM code/artifacts given that it would not be
possible to use the TPM eclipse IDE to talk to RTE due to eclipse
version mismatch?

Options:
1. Use the web UI to create folders and check in files which belong
to the TPM artifacts. Don't need to install any client for this.

2. Install RAD 7.5.x and RTC plugin on desktop. Create a general
project and create folders linked to the TPM artifacts created by
Eclipse 3.2.2. Check in files from within the RAD 7.5.x workspace
using the RTC plugin support. In this case the user needs to
install
another Eclipse instance and the RTC plugin on his desktop.

Has anyone tried working with TPM dev environment, to check in
code/artifacts into RTC repository?

What would be the best option?

Hi Geoff,

I didn't say I'd run into issues. I just happened to do the work around the way I described below. I think why I did that approach was because I didn't know RTC would work using the referenced project. This was very early in RTC 1.x.

I just couldn't imagine that one could unload and load projects in RTC when they where not directly located in the Workspace.
There where no sandboxes back then.

Would RTC be able to load and unload referenced projects located outside of a sandbox on windows?

Ralph

When I said "import the ToolX projects into RTC via reference", I meant
use "File -> Import -> General:Existing_Projects_into_Workspace" to
point Eclipse at the folders where the files already exist.

Cheers,
Geoff

On 10/8/2010 1:53 PM, gajjarps wrote:

Geoff:
Instead of copying files into a folder within Eclipse, I create a
folder that was linked to the folder on my desktop, which contained
files I wanted to check into RTC.
I am able to work with the files within Eclipse. However, eclipse/RTC
does not allow me to check in the linked files.
If I look at the file property - under source control, it clearly
states:

Ignored Due to: Linked resources are
ignored

Is there any way to make eclipse/RTC not ignore files which are linked
or are contained in linked folders?
Your help will be appreciated. Thank You.
..Pradeep

gmclemmwrote:
Hi Ralph,

Just for interest's sake, what problems did you run into if in step
2,
you imported the ToolX projects into RTC via reference, rather than

copy? In particular, this would allow you to skip step 4.

Cheers,
Geoff

On 6/25/2010 7:23 AM, rschoon wrote:
Hi,

in the past I had situations where RTC and other tools (ToolX
below)
would not run in the same Eclipse.

A strategy that did work was:

1. Create initial projects with ToolX
2. Import (copy) the projects into an RTC sandbox/workspace
3. Share the projects in RTC
4. Import the shared projects - no copy, just reference - back into
ToolX

Afterwards it is possible to develop with ToolX. and create/modify
files in the referenced Eclipse project.
From time to time switch to RTC and refresh the projects. RTC will
show pending changes. Check in changes and deliver.

Ralph

gajjarpswrote:
Our team uses Eclipse (version 3.2.2) TPM development environment.
RTC eclipse plugin is available for eclipse version 3.3.2 and above
(going to 3.5) for RTC version 2.0.0.2.

We need to start using RTC repository.

How do we check in TPM code/artifacts given that it would not be
possible to use the TPM eclipse IDE to talk to RTE due to eclipse
version mismatch?

Options:
1. Use the web UI to create folders and check in files which belong
to the TPM artifacts. Don't need to install any client for this.

2. Install RAD 7.5.x and RTC plugin on desktop. Create a general
project and create folders linked to the TPM artifacts created by
Eclipse 3.2.2. Check in files from within the RAD 7.5.x workspace
using the RTC plugin support. In this case the user needs to
install
another Eclipse instance and the RTC plugin on his desktop.

Has anyone tried working with TPM dev environment, to check in
code/artifacts into RTC repository?

What would be the best option?

A terminological note: by definition, files in the file system that are
under RTC source control are always in a "sandbox".

So the best way of phrasing the last question is "do sandboxes need to
be under the the Eclipse workspace root directory?" (i.e. in the
"default location" for new Eclipse projects). The answer to that is
"no, they can be located anywhere on disk". I believe that was true in
RTC 1.x, but that's so long ago, I can't be sure (:-).

In particular, when you put an Eclipse project under source control, and
that Eclipse project is located somewhere other than under the Eclipse
workspace root directory (such as by using the technique I describe
below), then that will automatically create a sandbox on disk above
wherever that Eclipse project happens to be located.

So general guidance: put an Eclipse project under source control where
it currently sits on disk, rather than copying it elsewhere.

There is one exception to this general guidance: when that Eclipse
project is under source control of some system other than RTC (and you
want to continue having it under source control of that other system).
It is tempting to try to put the same project under source control of
two systems at the same time, as a way of "synchronizing" changes
between those two source control systems (at least, it was tempting to
me :-). But there are at least a couple of problems with that (both
resulting from the fact that current IDE's only allow you to register
one source control system for a given set of files):
- The IDE's usually store in the file system some information about what
source control system is in use for that set of files ... and often in
the same file (Visual Studio does, for example). When you tell the IDE
that a set of file is under control of a different SCM system, it will
overwrite the content of those files.
- For systems that version control the names of files (such as RTC and
ClearCase), the source control system must be notified about such moves
.... but the IDE only knows about one source control system for a given
file area at a given time, so the other source control system won't be
notified, and file moves get lost.

Cheers,
Geoff

On 10/11/2010 5:38 AM, rschoon wrote:

Hi Geoff,

I didn't say I'd run into issues. I just happened to do the work
around the way I described below. I think why I did that approach was
because I didn't know RTC would work using the referenced project.
This was very early in RTC 1.x.

I just couldn't imagine that one could unload and load projects in RTC
when they where not directly located in the Workspace.
There where no sandboxes back then.

Would RTC be able to load and unload referenced projects located
outside of a sandbox on windows?

Ralph

gmclemmwrote:
When I said "import the ToolX projects into RTC via
reference", I meant
use "File -> Import -
General:Existing_Projects_into_Workspace" to
point Eclipse at the folders where the files already exist.

Cheers,
Geoff

On 10/8/2010 1:53 PM, gajjarps wrote:
Geoff:
Instead of copying files into a folder within Eclipse, I create a
folder that was linked to the folder on my desktop, which contained
files I wanted to check into RTC.
I am able to work with the files within Eclipse. However,
eclipse/RTC
does not allow me to check in the linked files.
If I look at the file property - under source control, it clearly
states:

Ignored Due to: Linked resources are
ignored

Is there any way to make eclipse/RTC not ignore files which are
linked
or are contained in linked folders?
Your help will be appreciated. Thank You.
..Pradeep

gmclemmwrote:
Hi Ralph,

Just for interest's sake, what problems did you run into if in step
2,
you imported the ToolX projects into RTC via reference, rather than

copy? In particular, this would allow you to skip step 4.

Cheers,
Geoff

On 6/25/2010 7:23 AM, rschoon wrote:
Hi,

in the past I had situations where RTC and other tools (ToolX
below)
would not run in the same Eclipse.

A strategy that did work was:

1. Create initial projects with ToolX
2. Import (copy) the projects into an RTC sandbox/workspace
3. Share the projects in RTC
4. Import the shared projects - no copy, just reference - back into
ToolX

Afterwards it is possible to develop with ToolX. and create/modify
files in the referenced Eclipse project.
From time to time switch to RTC and refresh the projects. RTC will
show pending changes. Check in changes and deliver.

Ralph

gajjarpswrote:
Our team uses Eclipse (version 3.2.2) TPM development environment.
RTC eclipse plugin is available for eclipse version 3.3.2 and above
(going to 3.5) for RTC version 2.0.0.2.

We need to start using RTC repository.

How do we check in TPM code/artifacts given that it would not be
possible to use the TPM eclipse IDE to talk to RTE due to eclipse
version mismatch?

Options:
1. Use the web UI to create folders and check in files which belong
to the TPM artifacts. Don't need to install any client for this.

2. Install RAD 7.5.x and RTC plugin on desktop. Create a general
project and create folders linked to the TPM artifacts created by
Eclipse 3.2.2. Check in files from within the RAD 7.5.x workspace
using the RTC plugin support. In this case the user needs to
install
another Eclipse instance and the RTC plugin on his desktop.

Has anyone tried working with TPM dev environment, to check in
code/artifacts into RTC repository?

What would be the best option?

Geoff,

thanks for the clarification. I will definitely try that just to understand the implications.
If I just could find some time.

Ralph