I am trying to use a network folder (in windows) as my Eclipse workspace. I have looked online for solutions for a fix for networks folders with no positive results. I am unsure if this is possible to do, a quick fix, or if there is additional Eclipse settings that have to be altered.
edit
I have on one computer my eclipse workspace, and that folder is shared with my HomeGroup (windows file sharing). It is also shared as a network folder.
I need to access these files on another computer without having to copy and paste the source to my secondary pc.
The reason it would not allow me to access the network folder was because the folder remained in its 'read only'state. After restarting my computer, it allowed me to change the folder properties to Read/Write allowing me to access the folder as an Eclipse workspace.
Related
I have an Eclipse PyDev project (Eclipse 4.7.3a). I want to be able to sync the Eclipse workspace between several computers (and that it works, obviously).
First problem : the Python virtual environment. I have installed it in a folder that is located next to the Eclipse workspace (but not inside it) and is also synced between the various computers.
Since the folders for the workspace and the Python virtualenv are not located at the same point the of file system (I use Linux), my guess the simplest way to achieve this would be to use some kind of environment variable, different on each computer, that would point to the directory that contains all the synced folders.
So how can I set a Python virtualenv using a kind of system environment variable ?
Or is there another way to achieve my goal (sharing and syncing an Eclipse workspace between several computers) ?
This is not currently possible.
The workspace has information which is dependent on the absolute paths and is not really shareable (unless you have a mirror in both computers with files in the same paths on both).
Some configurations can be saved in the project itself or in the user settings (the ones that can do that have buttons in the preferences page to save to a project / show from a project -- but note that the interpreter itself still doesn't have that).
Personally, what I do is save everything possible in the project and commit that to git (so, anyone using the project will use those same settings), and try to use the same paths on multiple machines.
I have a desktop and a laptop which i bring to uni. Is there a way to put eclipse workspace on One Drive (sky drive) and then be able to work on it from multiple computers? I have tried it but it seems to mess up the folders. I.e. the package folder is now a standard folder.
UPDATE:
I found this link but I'm not too sure it will work. Anyone willing to explain if this will work?
Here's the link: http://www.howtogeek.com/174765/how-to-sync-any-folder-with-skydrive-on-windows-8.1/
If you want to store the workspace there, you need to make sure that the project files such as .project and .classpath, which are automatically generated by Eclipse, are also stored. Otherwise, Eclipse won't recognize the folders as project directories.
Still even if you store all files you can encounter problems in some cases if you're using different versions of Eclipse across different computers, and with different plugins, features and so on. A simple solution is to also store the Eclipse installation itself so that you use the same Eclipse across all computers.
OneDrive does not (yet!) support syncing files that start with periods, like the .eclipse settings folders. Because of this you will not see those items sync over OneDrive.
Make NEW FOLDER in onedrive. Then run Eclipse with this folder. Run Eclipse with this folder in another computer.
I have opened Eclipse workspace that I transfered from another computer but it does not show any projects in package explorer (there should be a lot of them). Still project's folders are in workspace folder.
The new machine where I transfered the workspace runs Windows 7 that has the read-only folders issue (more here). That is all the folders that are created on that OS are read-only and that the read-only atribute cannot be removed in any way.
Eclipse originally refused to open the workspace at all saying that .metadata folder of the workspace is read only. After turning user control to the lowest level it opens the workspace but it acts as if it did not contain any projects. I think this is because Eclipse refuses to work with read-only folders and project folders are also read-only.
Did somebody have same problem? How did you solve it? Any suggestions are wellcome.
It is not enough to move your projects in the workspace path folder, you also need to import them. And because of they are in your path folder, you can't import them again because it will say you still have them in your workspace. Move them to another folder (for example in desktop), be sure your workspace folder is empty, and then try to import them from your temporary folder in desktop.
I want to create several workspaces which point to different branches of a codebase.
The problem I am facing is every time I need to create a new workspace I have to do the same configuration for each workspace.
Example:
Setting up tomcat configuration and it's related java options such as library and java agent settings.
A system variable that points to specific folder containg my jar files.
Another system variable
Questions:
is it possible to have these setups done once so that all subsequent workspaces do not need to be configured?
is it possible to export these preferences and import later into any workspace either on my machine or other machine?
System information:
Windows 7, Eclipse 3.5, Sysdeo tomcat plugin, Tomcat 6
While eclipse does have an Export preferences option, it does not export everything and specifically it is not comprehensive enough for workspace duplication.
In the past I have had a lot of success just cloning the physical workspace folder itself.
For example, let's say you have setup the workspace with everything that you want in it. To duplicate it, find out the path of the current workspace folder by going to File -> Switch workspace -> Other. The path shown here in the dialogue that pops up is the current workspace path ( don't press ok yet)
Create a copy of this folder. Now to use this copy, just use it in the above dialogue, i.e., go to File -> Switch workspace -> Other and put in the path of the copy. Press OK and Eclipse shall restart with the new workspace. Now the only thing you will have to do is point the code to a different branch. Rest all the settings should be present already.
This works specially well on the same machine. If you copy this workspace folder it should still work but your mileage may vary.
This question was close to mine, but not quite.
I have a Windows desktop and a MacBook Pro. I'd like to be able to keep my Eclipse workspace in my Dropbox folder. The problem is that many project settings change between platforms: references to JREs, JDKs, and other libs.
Every discussion I've seen of this problem seems to suggest taking advantage of the source control system's ignore functionality, so that such-and-such file remains local-only and thus able to remain platform-specific. But when you're working with a real single shared folder, that class of solution doesn't apply.
Have you had luck working with a Java Eclipse project living in a single folder shared over the network, cross-platform?
I have my Eclipse workspace inside Dropbox with all my project folders within, but use the new-ish "Selective Sync" feature of Dropbox to make sure that the .metadata folder is not synced.
This means my Mac and Windows machines have their own .metadata folders but the project folders remain in sync.
Seems to be working so far...
Use source control with individual workspaces. By doing it this way you lose the capability of two developers making changes to the same file. You also run a higher risk of people stepping on each other. With Subversion (or others) source control is free and gives you traceability.
Perhaps the way to have less problems is just to share the source folder, neither workspace settings nor bin folder.
Just put your source folder in Dropbox.
Create the project on site1 and then:
Right click over the project, choose properties
--> Java Build path --> Source tab
--> Link source button
Then create a link to your source folder in Dropbox and assign it a name (e.g. src2)
Make the same for site2.
All your source files must be in your share source folder in Dropbox.
Of course you must configure on each site the settings like libraries and other stuff but this task is less frequently and perhaps desirable because you have two different environments.
For anyone else having trouble getting this to work, try File->Import->General->File System. Be sure to select Create links in workspace from the Advanced options. Seems like the cleaner solution and you can keep using your usual workspace.