It's all about the answers!

Ask a question

SCM: what does "Overlaps detected in the projects to be shar


Christophe Elek (2.9k12921) | asked Oct 01 '09, 10:30 a.m.
JAZZ DEVELOPER
retagged Dec 03 '13, 4:44 p.m. by David Lafreniere (4.5k7)
I am trying to share a project into a component and I am getting this error

"Overlaps detected in the projects to be shared"

Which are the overlaps as I am trying to share only one project into a new
component into a new repository workspace ?

--
Christophe Elek
Jazz L3
IBM Software Group - Rational

Comments
Michael Bunnell commented Nov 16 '09, 4:08 p.m. | edited Mar 07 '15, 5:45 p.m.

Christopher - did you ever get a resolution to this? We are running across the same issue. Any help would be appreciated.


Geoffrey Clemm commented Nov 17 '09, 12:53 a.m. | edited Mar 07 '15, 5:46 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Chris and/or Michael,

Please create a workitem, and attach a zip of the project that you are
trying to share, to see if we can reproduce this problem.

Cheers,
Geoff



Christophe Elek wrote:

I am trying to share a project into a component and I am getting this error

"Overlaps detected in the projects to be shared"

Which are the overlaps as I am trying to share only one project into a new
component into a new repository workspace ?


Andrew Hoo commented Nov 17 '09, 1:51 p.m. | edited Mar 07 '15, 5:48 p.m.
JAZZ DEVELOPER

Michael, Christophe,

You'll have to describe your environment a bit more. Christophe, in your case overlaps shouldn't happen in the situation of sharing into a new component of a new workspace.

Are you trying to share into a sub-folder of a component, and that component is already loaded? This is essentially the case that defines an overlap.

Can you give us a description of the layout of your component as seen in the repository and the layout of the project in eclipse (including the new one you want to share?)

I can elaborate more on what overlaps really are and why we prevent them, but I don't want to drone on too much here. Instead we can focus on getting your project shared.



Christopher - did you ever get a resolution to this? We are running across the same issue. Any help would be appreciated.


Gabriel Valencia commented Aug 27 '10, 6:16 p.m. | edited Mar 07 '15, 5:48 p.m.
Note: We were able to get Michael up and running ... there were files in
the file area left from a previous share project that collided.



I'm getting the same error in a slightly different scenario perhaps. I have two streams each sharing one component. However, each stream has a different set of baselines. One stream is already loaded into a repo workspace.

I created a second repo workspace for the second stream. It doesn't have anything in it yet but I loaded it so that I can upload some code for our project. It is loaded in this dir: C:\RTC\snapshot8407

I am now trying to share an Eclipse project into this second repo workspace and I end up getting the same error. The Eclipse project is in this directory: C:\RTC\snapshot8407\iice. I am simply right clicking on the project and sharing it via the Team menu.

I have a feeling the way I have the snapshots set up is causing the conflict. What would be the typical way to share an eclipse project in this kind of scenario?

2 answers



permanent link
Luiz Almeida (23014170) | answered Oct 22 '13, 9:14 a.m.
edited Oct 22 '13, 9:14 a.m.
I solved this problem unloading the component that I wanted to put my project. With the component unloaded, I share the project correctly.

Comments
1
Rudolf Pailer commented Apr 12 '14, 11:36 a.m. | edited Mar 07 '15, 5:47 p.m.

The procedure describey by Luiz Almeida worked for me as well. Unload the component and share the new project with the component unloaded.


Tiia Laitinen commented Feb 10 '15, 5:57 a.m. | edited Mar 07 '15, 5:47 p.m.

Unloading the component solved the problem for us too.
-unload component and then share project without loading component first.


permanent link
Geoffrey Clemm (29.6k23035) | answered Nov 17 '09, 6:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Mar 07 '15, 5:52 p.m.
Note: We were able to get Michael up and running ... there were files in
the file area left from a previous share project that collided.

Your answer


Register or to post your answer.