Community
Participate
Working Groups
Build Identifier: 20110615-0604 Eclipse is not prompting for a workspace directory regardless of the preferences setting at General>Startup and Shutdown>Workspaces>Prompt for workspace on startup Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. No workspace directory prompt appears. 3.
Are you passing any command line arguments to eclipse when you start it?
Created attachment 198574 [details] My eclipse.ini configuration
Created attachment 198575 [details] My config.ini
No, it's pretty much the standard J2EE download. But I have installed several plugins. I'll try unziping the fresh download again and seeing what happens.
There is a known bug pattern where a plugin asks for the workspace location before the prompt can occur. This causes it to force a default location and the user is never prompted. If this is the problem, it's certainly possibly caused by any plugin. So, trying a fresh install is a good first step. Thanks for following up.
When I unzipped my J2EE download and ran it clean without any plugins, it is prompting me for a workspace. I restarted several times and it continues to prompt me. The one that I built yesterday with all of my plugins will never prompt me not matter what I try. So I guess the work around is to start over and reinstall all of my plugins again. Thanks for your help.
As John mentioned this is most likely a problem with one of the extra plug-ins that you have installed accessing the workspace data area before it has been set (and before the prompt has come up). Closing.
I've just experienced this for the first time on HELIOS. It was never a problem until I installed the Spring plugin. I plan to migrate to INDIGO soon. I have it installed and it's NOT happening there even though Spring is installed.
(In reply to comment #8) > I've just experienced this for the first time on HELIOS. It was never a > problem until I installed the Spring plugin. > > I plan to migrate to INDIGO soon. I have it installed and it's NOT happening > there even though Spring is installed. And now by reverting to the previous config, the problem has gone away.