Bug 274789 - Support sparse checkouts in Team Project Set
Summary: Support sparse checkouts in Team Project Set
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 04:16 EDT by Baptiste Mathus CLA
Modified: 2019-09-06 16:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Baptiste Mathus CLA 2009-05-04 04:16:52 EDT
Build ID: M20080911-1700

Steps To Reproduce:
1. Using Subversion, checkout a project non recursively (equivalent of the -N option for CLI)
2. Export this project with project Set
3. Delete this project from your Eclipse installation or open another workspace
4. Import the newly created .psf in Eclipse
5. Notice that it download the whole project tree, not only the directory root (using sparse checkout)

More information:
Since 1.5, subversion offers a feature called "sparse checkout" which lets you specify if you want the whole tree of a given directory or if you want it to be retrieved non recursively (and following updates will know that).

Currently, the exported .psf file format does not store the sparse parameters. The form is looks like the following:

<?xml version="1.0" encoding="UTF-8"?>
<psf version="2.0">
<provider id="org.tigris.subversion.subclipse.core.svnnature">
<project reference="0.9.3,svn://svnserver/project-url,ProjectName"/>
</provider>
</psf>

It would be great if the "team project set" feature would be able to also restore the "sparse checkout" parameters.

Cheers.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:12:35 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.