Bug 3101 - Import/Export projects (1GIEJTL)
Summary: Import/Export projects (1GIEJTL)
Status: CLOSED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 5827 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 22:49 EDT by Rodrigo Peretti CLA
Modified: 2005-05-10 14:55 EDT (History)
5 users (show)

See Also:

Attachments
import .project and relative pathnames in .classpath needed (597 bytes, text/plain)
2002-03-26 09:40 EST, Markus Kohler CLA 		no flags Details
View All 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 Rodrigo Peretti CLA 2001-10-10 22:49:27 EDT 
Having read a post (Project Metadata) in the newsgroups, it sounds like a good idea to have
the projects as isolated pieces as much as we can. This isolation could impact the way we
persist a project's metadata, since resources are already separate.
	This isolation would be linked to two more API's for IWorkspace:
		- import(InputStream project)
		- export(OutputStream project)
	Two suggested solutions:
	1) Separate the metadata on disk
	2) Separate on-the-fly when exporting

	It sounds good when the user wants to share projects but not necessarily create a version
of it on a VCM repository. Another advantage would be the possibility of exporting the local history
as well.

NOTES:
Comment 1 DJ Houghton CLA 2001-10-24 06:44:25 EDT 
PRODUCT VERSION:
	129
Comment 2 John Arthorne CLA 2001-11-13 10:52:52 EST 
*** Bug 5827 has been marked as a duplicate of this bug. ***
Comment 3 Rodrigo Peretti CLA 2001-11-26 14:44:11 EST 
A proposal was posted on the platform-core-dev mailing list and will be 
discussed on the mailing list. Feel free to join and discuss.
Comment 4 DJ Houghton CLA 2002-03-23 09:24:38 EST 
As of build 2002-03-19, the project description is included in the project 
content area in a .project file. This file is sufficient for project 
interchange between workspaces.

Moving to Platform/UI for consideration of a project import/export wizard.

Notes: 
  - see IProject.create
  - team_private_members (e.g. the CVS folders) must not be included in a stand-
alone project zip file which is to be used with a different workspace
Comment 5 Markus Kohler CLA 2002-03-26 09:40:34 EST 
Created attachment 518 [details]
import .project and relative pathnames in .classpath needed
Comment 6 Markus Kohler CLA 2002-03-26 09:42:08 EST 
Sorry for attaching my comments, I just didn't see this from
Comment 7 Nick Edgar CLA 2002-04-04 12:30:53 EST 
We need an import wizard to allow an existing project in the filesystem to be 
added to the workspace.
Comment 8 Tod Creasey CLA 2002-04-05 15:27:02 EST 
Import project wizard added for build >20020405
Comment 9 Tod Creasey CLA 2005-05-10 14:55:59 EDT 
Marking closed