Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 83276 - Change configuration on startup
Summary: Change configuration on startup
Status: RESOLVED DUPLICATE of bug 106169
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-20 01:59 EST by Xavier Méhaut CLA
Modified: 2006-03-29 09:46 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Méhaut CLA 2005-01-20 01:59:55 EST
Hello,
I would like to suggest an enhancement for the functionnment of separate
plugins... Up to now, we can set our plugins into separate directories and then
refreneced them in to links directory... I would likre to propose to mimic the
starting of the workbench when we can choose the workspace we want to use, ie
the ability at launch to choose also the set of external plugins directory we
want to use...
Example : we have the following firectories 
eclipse/plugins (default)

myPath1/GEF
myPath1/EMF

myPath2/Omondo

myPath3/PhpEclipse

and the following external configuration files :
myConfig1.xml containing Omondo, EMF, GEF
myConfig2.xml containging only PhpEclipse

At start, we could choose to use the config1 or the config2...with the same
eclipse installation... It should be convenient for a developper alone, but more
  for a team...
regards
Xavier
Comment 1 Jeff McAffer CLA 2005-01-20 10:15:54 EST
This is interesting and related to the ability to login and have different sets 
of plugins run depending on the user.

moving to update.  Update is in complete control of what plugins are installed 
as well as being the one who defines the notion of links dirs.
Comment 2 Dorian Birsan CLA 2005-01-20 10:40:26 EST
It looks like what is needed is:

1. the ability to store the existence of multiple configurations somewhere, 
let say as eclipse/configuration/configurations.xml.
That file (configurations.xml) will contain the name and location to the 
available configuration (config1 and config2).

2. When eclipse starts, the user is prompted to pick up a configuration, much 
like the way it is prompted to pick up a workspace.

The problem I see with this part is that, unlike prompting for the workspace, 
prompting for the configuration must happen before any plugin runs.
Basically, the code would have to be in the EclipseStarter. 
Jeff, comments ?
Comment 3 Xavier Méhaut CLA 2005-01-20 11:46:07 EST
an additional comment : 
What I see as benefit of such architecture too, is the fact we should be able to
improve the rapidity of the workbench... For my own experience, I used to use
only one eclipse installation for all my projects (I've several workspaces for
each kind of project)..My projects can be of very different natures :
* a web site/intranet made in Php
* a web site (bug report tool) made in Jsp
* a project for cartography (geotools) and Mysql
* a groovy project
Currently my plugins directory has a lot of plugins which have not to work
systematically together...and I imagine that this must have an impact in a
certain way on performances of the workbench (maybe not ;) )
regards
Xavier
Comment 4 Dorian Birsan CLA 2005-01-24 10:20:54 EST
Moving to Runtime:
Jeff, see my comment #1: this request is not about the links file, but about 
the ability to pick which configuration to run with. The support is already 
there, because the user can pass -configuration. What is missing is having a 
dialog that prompts the user to select a configuration.
It looks like EclipseStarter or eclipse.exe should be the place to prompt.
Comment 5 Jeff McAffer CLA 2005-01-24 11:36:11 EST
yes and no.  This is the standard bootstrapping problem.  In order for us to 
ask anything we need SWT etc.  To get SWT etc we have ot be running some 
configuration or duplicate a large amount of code and have various undesireable 
side effects.  

So yes, I was wrong to put this over to update (my apologies) and no, we can't 
really do anything about it either.  EclipseStarter or Main are too early.  We 
have been searching for ways to do this and welcome any suggestions.

Note, having eclipse.exe ask is not an option.
Comment 6 Pascal Rapicault CLA 2006-03-29 09:46:00 EST
Closing as dup.

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