Bug 37744 - Add support for multiple workspaces
Summary: Add support for multiple workspaces
Status: RESOLVED DUPLICATE of bug 37681
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-16 05:19 EDT by Oyvind Harboe CLA
Modified: 2003-05-21 14:55 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 Oyvind Harboe CLA 2003-05-16 05:19:03 EDT
I'm working on two versions of our product at the same time(main + sp branch).

The thing that first came to mind was to check out both, but I got collisions 
with project names.

The second idea was to have multiple workspaces, one for each branch, but that 
does not appear to be possible(I could install Eclipse multiple times).
Comment 1 Rafael Chaves CLA 2003-05-16 11:45:32 EDT
Eclipse install and workspace locations are not related. The default workspace 
location is in the current working directory. The -data option allows you to 
define a different location for the workspace. For more info search 
for "Running Eclipse" in the Eclipse help or go to (URL may be split):

http://dev.eclipse.org/help21/index.jsp?
topic=/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
Comment 2 Oyvind Harboe CLA 2003-05-16 17:26:08 EDT
I have taken the liberty to reopen the bug(this is afterall a feature request, 
not a bug-report).

The suggested approach is clunky, because preferences and configuration options 
are stored in the workspace.

When working on two branches, I'd like to share e.g. Java formatting options, 
etc. Only the projects should be stored in different places.

Øyvind
Comment 3 Rafael Chaves CLA 2003-05-18 18:02:53 EDT
So what is being requested is workspace-independent properties, right?

Support to more easily changing the current workspace is addressed by bug 37681.

Also, you can checkout a module from a CVS repository with the name you want
(check out as...). This would allow you to keep different versions of the same
project in the same workspace. It won work if this project is referenced by
others, though.
Comment 4 Oyvind Harboe CLA 2003-05-19 03:08:30 EDT
>So what is being requested is workspace-independent properties, right?

What I really want is a smoother way to work with branches. Good multi-
workspace seems to be a fairly generic tool that should do the job.

>Support to more easily changing the current workspace is addressed 
>by bug 37681.

Excellent.

>Also, you can checkout a module from a CVS repository with the name you 
>want (check out as...). This would allow you to keep different versions 
>of the same project in the same workspace. It won work if this project 
>is referenced by others, though.

I'm relying on the names of the projects for my ant scripts to work. Renaming 
the projects is not an option.

I did try to make a java project a sub-project of a resources(simple) project, 
but that changed the project type.

Øyvind

Comment 5 John Arthorne CLA 2003-05-21 14:55:26 EDT
Closing again.  This issue is covered by other bug reports.  Bug 36965 for
sharing preferences between workspaces, and bug 37681 for an easier way to
switch workspaces.  Please CC yourself on this bug reports if you are interested
in following progress.

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