I need to design or use 5 to 10 PCs (with eclipse) but with the same workspace, how can I do that? I already tried but I can not share the folder of the workspace, please help
What do you want to achieve, actually?
Because the workspace is supposed to be user specific. It contains things like settings, how perspectives are setup, which view to show where. Which means if two users share a workspace they will continually write of each others settings.
And to enforce this, as soon as you starts Eclipse with a workspace, it is locked preventing someone else to use it.
So sharing workspace is not a good idea.
What I guess you really want to achieve is to share the projects between several developers. Using project sets is a good way to do that. Check out my answer for a different question regarding this.
If you want to share preferences with other users, then check out this question for advice on import/export of preferences.
Related
This might sound like a stupid question to ask, but I'm curious if it is possible for others to view and reach different user's eclipse projects?
I know there is GitHub, but I have not leashed my workspace to a central source or cloud such as Git. Just a question regarding privacy and security.
Let's say you are coding a program in Java with eclipse and it might contain some sensitive information. Is the project completely safe on your computer? Or are there any settings you need to change in order for it to be secure? Like setting a password on the workspace or so?
Thanks in advance guys.
When Eclipse is started, it asks you for a workspace location. Anyone who has access to that location would be able to view your workspace.
To view your current workspace location go to: File -> Switch Workspace -> Other...
I've been searching and searching for what the purpose is for a workspace. I've asked this question in stack chats but no one seems to know.
I know workspaces are local copies of solutions and you can switch between them when testing different things on the same projects but with different branches but I can do that with standard folders as well. So I can't figure out what the advantages and disadvantages are of using workspaces over normal folders. Is having different settings for each workspace the only advantage?
The only other obvious thing I see is shown in the screenshot but that a workspace is shown as a single "Code Workspace" file with no folder structure even though it does have one while standard folders have the structure and shows all contents.
I found this article on stack and it's kinda relevant but not as specific and it's unanswered. So instead of setting a bounty I thought I'd ask exactly what I was looking for. Asking about workspaces with settings vs user settings.
Two things which makes Workspace different from standard folders -
Like the other answer you linked to, you can have workspace based settings
In one Workspace you can open different folders which are not necessarily in the root folder which you open first.
In addition to workspace-based settings, workspaces can act like aliases that can link to a root folder (sort of like Dreamweaver's Sites feature). So you can keep a centralized folder/collection of all your workspaces in one place for easy navigation (a folder named VSC-Workspaces for example), yet they can point to and open work folders that may be saved in different locations on your hard drive, since they might be websites or python files, etc.
I like to use several different workspaces, so as to keep everything organized. However, its annoying to have to copy the .settings folder to all my workspaces just because I added a keyboard shortcut. I'm looking for a way to update the preferences of all my workspaces whenever I change the preferences in one workspace. The settings I care about are keyboard shortcuts, code style, fonts, etc.
I have found this plugin which might be useful, but doesn't seem to be exactly what I'm looking for.
Ideally, I could have my settings saved in the cloud somewhere. On startup, Eclipse will check if workspace settings and the settings in the cloud differ, and if so, import them from the cloud. If I change any settings, then these preferences should be exported to the cloud. This way I also have my preferences on my school's lab machines.
Does anybody know a way to make this work? I'm all ears.
Thanks
Short answer: no. The easiest thing is probably just manually configure your preferences on those two or three PCs where you use Eclipse, and move on.
Longer answer: yes, you can copy (and standardize) Eclipse settings (e.g. for a standard configuration across your development shop). Here's a good article explaining how:
http://www.javalobby.org/java/forums/t18678.html
Finally, there's still no easy way (AFAIK) to safely and reliably UNINSTALL plug-ins as of the latest/greatest version (Indigo, Eclipse 3.7). So if you find yourself experimenting with a lot of plug-ins .. some of which you might ultimately wish to get rid of ... then maybe your best bet is installing Eclipse on a VM (say, VBox or VMWare, running Linux or Windows). Use your VM as a little "sandbox" where you can try stuff out, and easily clone (if you like it) or blow it away (if you don't).
IMHO...
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
I am trying to setup eclipse and the project/workspaces to works smoothly and efficiently over 3 different computers (not in the same LAN).
Right now I have to do this in every computer:
install a plugin
customize eclipse.ini
customize prefs (I'll keep prefs.epf inside \eclipse folder and keep it synched with care)
I would like to avoid it so I won't end up with different versions of plugins etc in different computers. In order to achieve this, I have decided the following:
\eclipse distribution
I intend to put my \eclipse distribution under Dropbox. The reason for that is to use the exact same eclipse install in the 3 computers I use.
Projects
Projects (src and all resources etc) are synched by using SVN/Hg (I keep some projects under one, others in the other). No problem here. But the same project is stored in different drive/path in different computers (C:\projects\projectA and D:\projectA for example).
Workspaces
I use a different workspace for each project (or group of related projects). So I run eclipse with
-data \path-to-.metadata
My question is, where do I put worskpace folders, and do I synch them?? I have two options:
I keep workspaces inside Dropbox, this way they are synched automaticaly. But will it work?? As pointed out previously the same project can be in diff drive/path in two computers. This is the approach taken by this stackoverflow guy, but not sure if he had diff. drives etc.
I keep workspaces outside Dropbox, they are NOT synched. My question here is whether the same \eclipse will open -data \workspaceAInComputerA and then later open -data workspaceAInComputerB having both same names, projects etc but being totally separate workspaces.
It sounds a bit convoluted maybe but I think it's worth setting it right for long term usage. Anyone can recommend a setup??
thanks
ps: I don't want to keep taking a usb with me so don't suggest any 'portable eclipse' thing please!
This guy seems to have put his workspaces in Dropbox and it seems to be working for him. Personally, I'm putting the Entire eclipse directory + some sdk's in dropbox - we'll see how that goes!
UPDATE: This went horribly wrong for me - just going to use svn/git