Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 193191

Summary:	[Sync Info] Copying folders between projects of the same repository is problematic
Product:	[Eclipse Project] Platform	Reporter:	DJ Houghton <dj.houghton>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	john.arthorne, simon_kaegi
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description DJ Houghton

2007-06-18 16:20:42 EDT

build i0608-1718

I'm not sure how I got into this state but its happened twice to me now. Basically I have a workspace for all my Orbit projects and since we can have multiple versions of each project, the projects in my workspace are named:
  org.apache.lucene_v1.9.1
etc.

But somehow I get into a state where I make a change to a file in one project (org.apache.lucene.analysis) and in the Sync view it shows up as an out-going change to the org.apache.lucene project, which is incorrect.

I checked the CVS properties in the project properties and the paths to the projects in CVS seem correct. I also checked the contents of the CVS folder in the file-system and the paths, etc look ok here too.

Note that I have multiple versions of the lucene project in my workspace but a single version of lucene.analysis.

Deleting both projects from my workspace and starting over seems to help but is a rather unfortunate work around.

Any ideas?

Comment 1 Wassim Melhem

2007-06-18 16:25:23 EDT

How is this a PDE issue?

Comment 2 DJ Houghton

2007-06-18 16:32:07 EDT

I thought you might be interested since you did a lot of work to get developing multiple versions of the same bundle to work. :-)

I will move to Team and we'll see what Michael thinks.

Comment 3 Michael Valenta

2007-06-19 11:24:22 EDT

Did you happen to do any copying between projects? That's the only thing I can think of that may have resulted in what you are seeing.

Comment 4 DJ Houghton

2007-06-19 15:01:07 EDT

Not sure if I was copying or not but I might have been. I was making changes to about.html (and related) files to several bundles at once so I might have been copying things around.

Tom and Simon have also mentioned that they've seen similar issues.

Simon mentioned that his problem was when he copied files between projects when both projects were in branches.

Comment 5 Michael Valenta

2007-06-19 15:14:16 EDT

It's doubtful that copying files would be a problem. However, copying folders is almost guaranteed to cause problems if the source and target project are in the same repository. Is there any chance that you copied (or moved) folders.

Comment 6 Simon Kaegi

2007-06-19 15:24:57 EDT

Definitely a possiblity at least for what I was doing.
As I recall I was moving the contents of about_files around and may have been copying the whole directory.

Comment 7 DJ Houghton

2007-06-19 15:34:57 EDT

Yes, I might have also been copying about_files/.

Comment 8 Michael Valenta

2007-06-21 11:25:46 EDT

Unfortunately, this is caused by the way CVS stores it's meta-data. It is next to impossible to detect the difference between cases were the meta-data should be kept and those for when it should be purged. We may be able to do it by implementing an EFS that was used for all CVS projects but his is a major undertaking.

Comment 9 DJ Houghton

2007-06-21 11:43:38 EDT

This issue results in lose of data, release of content into the wrong projects, and forced a rebuild of the Eclipse SDK post-RC4. Is it really a P5 priority?

Comment 10 DJ Houghton

2007-06-26 09:58:58 EDT

What sync-info is being stored? Where is the code to look at? Is there a document or javadoc describing how things work?

Comment 11 Michael Valenta

2007-06-26 10:52:11 EDT

The problem is that, for CVS. the metadata is stored in the CVS folder inside the folder being moved or copied. So the code in questions is in the Resources plug-in and the Filesystem plug-in. There isn't really an javadoc or Eclipse documentation about this since it is a feature of CVS itself. What I was trying to say in comment 8 is that the best solution I can see would be for CVS/Core to wrap the filesystem for any projects mapped to CVS so that it could exclude the CVS sub-folders from resource operations such as move and copy.

Comment 12 DJ Houghton

2007-06-26 11:21:53 EDT

John, is there a flag in IResource#copy that says not to copy team private members? I don't see anything off hand... Or do you have other recommendations? Perhaps a post operation listener that trims team private members from the destination?

Comment 13 John Arthorne

2007-06-26 14:50:55 EDT

No, no, maybe.

Comment 14 Eclipse Webmaster

2019-09-06 16:10:57 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 15 Eclipse Genie

2021-12-16 10:28:03 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.