Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336216 - [server] Private clone stays on the server forever
Summary: [server] Private clone stays on the server forever
Status: CLOSED DUPLICATE of bug 340553
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tomasz Zarna CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-03 06:04 EST by Szymon Brandys CLA
Modified: 2011-08-30 10:21 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Brandys CLA 2011-02-03 06:04:49 EST 
If we create a new top-level folder and link it to a Git repo, a private clone for the user is created on the server. This private clone will be shared by all top-level folders linked to the same repo.

However if all top-level folders pointing at this private clone are deleted, the clone stays on the server. So far I would just delete it. When we provide the Git shell (Bug 336116), the user should have more control over it.
Comment 1 Tomasz Zarna CLA 2011-03-08 05:41:40 EST 
Clones created in the user area[1] are linked to projects in workspace. Removing a project doesn't remove a linked resource[2]. Not sure if there is anything we can do, without changing that policy.

Added a test[3], ignored for now.

[1] bug 338558
[2] org.eclipse.orion.internal.server.servlets.workspace.WorkspaceResourceHandler.removeProject(WebProject, String)
[3] d0ba29457fff54cf34235a830b7fe15b74bf2a9c
Comment 2 Szymon Brandys CLA 2011-03-30 09:41:38 EDT 

*** This bug has been marked as a duplicate of bug 340553 ***