In Eclipse IDE you have the concept of "workspaces" allowing you to manage/view your projects in one side pane easily and allowing you to switch between projects easily.
As i gather IntelliJ doesn't have that feature because everytime when i open a new project it always asks to either open in a different window or same window? And in the latter option it overrides my existing open project.
You're right; IntelliJ simply doesn't have this functionality. Each project is opened in a single window, either overwriting your current window or spawning a new window.
If you feel that this sort of behavior is something you want, then feel encouraged to put in a feature request on their issue tracker.
You can create a new empty project and import into it the modules from the other projects.
This works for me, although is not exactly the same as what you're trying to achieve. Note that you will lose (e.g. have to specify manually) the specific projects' settings.
Related
This is about a peculiar habit of the Project Explorer in Eclipse that has been bugging me for years now.
If I expand some source subtree somewhere among my projects and then have to re-think which file I actually need to open, I often switch back into some other part of my project tree to find the info I need.
But, more often than not, when I actually did find that info and know which file exactly I need to open, the source tree I have expanded earlier has been collapsed again by eclipse (probably because it decided that it has to do a quick workspace rebuild or gradle refresh or something in that vein). Even worse, sometimes eclipse reorders the submodules of the (maven/gradle) project so that the subtree I have expanded earlier isn't at the same position in the project explorer anymore and I need to go looking for it again. Eclipse sometimes even (apparently randomly) starts to reorder the tree in the moment just before I want to click on a file or something like that.
So. How can I configure Eclipse to never collapse a subtree in the project explorer that I expanded manually? And how can I prevent Eclipse from reordering the projects? (Switching the IDE is out of question for this particular project, because there are some eclipse-only plugins for the framework involved.)
Some time ago I edited a node project in grails. Now every project, even if it has nothing to do with node, shows 5 node files when I do "new" to create a new file. (type script, node project file etc).
I now only have a grails 3 projects in Eclipse, with the usual groovy eclipse plugins installed.
When I want to create a new groovy file (e.g. a domain object, controller etc), I go to file->new, and I only see the 5 node entries, plus a few generic ones.
Is there any way to make it show "groovy class" in the new list, and not show the node related ones?
I thought facets might be for this, but my project has no facets configured (and eclipse still thinks its node), and there are no grails/groovy type facets).
Any suggestions? Not a show stopper obviously.
E.g. can I create my own facet without coding, or can I influence which file types appear on create new by project?
I could open up a DOS command box and do the grails command to create the classes, but his is more work, especially as it creates broken tests which have to be manually deleted after (until such point as we need tests)
Intellij ultimate is unfeasibly expensive, so that is not an option.
You should be able to customize what appears in the New drop-down using Window > Perspective > Customize Perspective.... In the dialog that comes up, click the Shortcuts tab and you can check or uncheck items that will show in the New drop-down.
You can also edit what options will show for the Show View and Open Perspective sub-menus from here.
I have a folder hierarchy that looks like this:
- workspace
- some_folder
+ eclipse_project
Is it possible to open and view the hierarchy in the project explorer of Eclipse beginning at "some_folder," instead of at "eclipse_project?" If so, how is this accomplished? When I try importing, Eclipse obviously refuses to because the files in the outer folder are already in the workspace.
Or does this contradict the principle behind Eclipse and projects?
Thanks.
Or does this contradict the principle behind Eclipse and projects?
Yes, it does. The File menu does offer to let you Open File..., but whether it's supported by an editor and how much functionality is retained is entirely up to that editor. Some will flat-out fail.
As a workaround, you can create a New General->File, expand the Advanced section of the wizard, and set the new in-workspace file to link to the real file's physical on-disk location, as long as that location is not in some way under the workspace's location. Note that even this may not always be supported by extremely old editors.
I have been using eclipse for a few years. I typically use just ONE workspace and have several projects for all of my perforce branches. I close the ones I'm not working on, open the one I am interested in.
The caveat to this approach is that I have to manually close empty editor tabs every time I do this.
Am I approaching this the wrong way?
I'm really not a fan of having multiple workspaces as then I have to setup proejct variables for each new workspace.
Is there a way to associate the currently open set of editor tabs to the current project(s)?
Thank you for your time.
-Dennis
Is there a way to associate the currently open set of editor tabs to the current project(s)?
AFAIK, no. However, you can associate the editors to a task by using Eclipse Mylyn. This way when you switch to an old task, it will set the editors and package exlorer to only show what you worked on the last time.
If you are working with defects from Jira or Bugzilla or a few other systems, these defects can automatically be imported into mylyn and will allow for very easy context switching.
If you dont get tasks from one of the supported repositories you'd have to manually create the tasks, but then just creating a dummy task for each project you work on would create the effect you are after.
I write code in several languages (Python, C, C++, and Java) using Eclipse. Is it possible to designate a directory on my machine (say /home/workspace/) as the "primary" workspace for any Eclipse session, but then to have subfolders, /home/workspace/python, /home/workspace/java, etc., in which I can create new Eclipse projects.
I don't want to have to navigate menus and select different workspaces for each session of Eclipse that I start up. I would rather just always have permission to manipulate any projects from a variety of folders at any time, but I can't find a clear answer about whether this can be done and how to do it.
As I understand your question; You want to have one workspace, but be able to code in several different languages without switching workspace but at the same time keep the projects separated?
First I would suggest you consider several workspaces, I find it convenient to keep settings and projects in separate workspaces. I rarely have to switch language that often.
But. I think what you want to do is to keep several working sets. You create one java working set, one C++ set and associate your different projects with a working set. Then you can minimize the java working set when you are running C++. For working sets you dont need any subfolders on the harddrive.
You might also want to look into Mylyn. Its a great tool for those who often are switching context. It saves the context (eclipse perspective, open files, etc) as associated with a task.
How about setting Eclipse to prompt for the workspace at launch? It wouldn't allow you to work in two languages at once, but should do the trick otherwise.
An Eclipse workspace can contain projects slated for different languages and those projects can live anywhere on your hard drive. There are at least two ways to do what you want. When creating a new project, uncheck the Use default location checkbox and browse to or specify the folder where you want your project to live. If a project already exists import the project into the workspace using the File->Import menu option and then select Existing Projects into workspace. In the next screen make sure the checkbox for Copy projects into workspace is not selected. This will leave the source files in the original folder.
In the Project explorer view, all the projects are going to look like they live at the root level. However you can group related projects into working sets. Then select just the working set you're interested in and all the others will disappear from view.
A warning is in order if you make use of eclipse variables in external tools (and possibly elsewhere). The syntax you use for paths needs to be adjusted. For example with projects outside the workspace this syntax ${workspace_loc:/MyProject/MyFile.txt} is no longer the same as this syntax ${workspace_loc}/MyProject/MyFile.txt