It's all about the answers!

Ask a question

RTC confused when copying a project


David Wall (111) | asked Sep 14 '11, 3:38 p.m.
Environment = Eclipse (Helios) + RTC source control (Version: 2.0.0.2 Build id: I20110128-1600

Windows XP (re-created on a linux system)

I have a non-trivial Web Application that I want to duplicate for a new application. The existing project is already under source control. I create the project by selecting the existing project, Ctrl-c, Ctrl-v. That is, use copy / paste to create the new project. Eclipse realizes this is a project copy so it prompts me for my new project name. Eclipse completes the copy. I update the implementation classes. I am now ready to push the new project into RTC. The problem is the new project is sort-of partially in RTC. I select the properties of the project and there is a Jazz Source Control item listed, but only provider and Location URI are filled in. When I right-click "team", I see the normal RTC options (check-in, deliver, ...) but there is nothing under the pending changes tab so the project is not really on the server. Looking at the jazz properties of the original project I see a large number of items on the page (provider, location URI, local full path, state, ... UUID). What I really expected is to see "share project" when I right-click on team on the new project.

I was a able to get out of the box. I exported the project to the file system, then copied the files to another system. On that system I imported the project. The team option now correctly realizes the project is not under source control and I can add it.

Summary -- copy / paste a project messes up the RTC settings of the target when the source project is already in RTC.

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Sep 14 '11, 11:32 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There is a folder in the file system that contains information about RTC
source control ... the .jazz5 folder. I'm guessing that you copied that
folder as well. Delete that folder after you do the copy (or don't copy
it in the first place), and you shouldn't have that problem.

But more importantly, why are you creating a copy at all? Why aren't
you just creating a new stream based on the files that are already under
source control.

Cheers,
Geoff

On 9/14/2011 4:08 PM, dawall wrote:
Environment = Eclipse (Helios) + RTC source control (Version: 2.0.0.2
Build id: I20110128-1600

Windows XP (re-created on a linux system)

I have a non-trivial Web Application that I want to duplicate for a
new application. The existing project is already under source
control. I create the project by selecting the existing project,
Ctrl-c, Ctrl-v. That is, use copy / paste to create the new project.
Eclipse realizes this is a project copy so it prompts me for my new
project name. Eclipse completes the copy. I update the
implementation classes. I am now ready to push the new project into
RTC. The problem is the new project is sort-of partially in RTC. I
select the properties of the project and there is a Jazz Source
Control item listed, but only provider and Location URI are filled
in. When I right-click "team", I see the normal RTC
options (check-in, deliver, ...) but there is nothing under the
pending changes tab so the project is not really on the server.
Looking at the jazz properties of the original project I see a large
number of items on the page (provider, location URI, local full path,
state, ... UUID). What I really expected is to see "share
project" when I right-click on team on the new project.

I was a able to get out of the box. I exported the project to the
file system, then copied the files to another system. On that system
I imported the project. The team option now correctly realizes the
project is not under source control and I can add it.

Summary -- copy / paste a project messes up the RTC settings of the
target when the source project is already in RTC.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.