How can I exchange workspace between ubuntu and windows xp?

I am using ubuntu 8.04 and windows xp. I am mounting a fat32 drive that contains the eclipse workspace for ubuntu. but I believe that I can’t use the workspace, maybe I don’t have the right to use it.

The bold disk installed on it has 755 to the right, I'm trying to use chmod to change it to 777, but failed. I am trying to set it to 777 mode, but I found that there is nothing in vfat mode.

How do I do next? How can I split the workspace? Help me. Thank you

+4
source share
4 answers

Instead of trying to share raw workspace data between two different systems, I suggest doing this as in typical large software development projects. Use a version control system to store code and commit / update for this version control system and from it instead of file sharing.

This may not be the answer that you were originally interested in, but be sure, you will notice many advantages of this version control system after a while, including:

  • It’s easy to get back to the code version before today's “genius” changes that didn't really work at the end.
  • There is a backup of your project if your workstation dies
  • You can even access your project from a completely different machine / location.

If your project is open source, you can use public services like Sourceforge.net .

+3
source

I believe that fat32 does not support the same permissions as Linux that you are familiar with. After you sort the rw option in /etc/mtab , then I think you will have a better time.

However, the step after this is to have two different Eclipse installations work in the same workspace.

I did not have much success with this (although you have not tried that this is an exact scenario), but I would be careful:

  • sync eclipse versions
  • Use only relative paths and relative to the work area. This is probably good practice, but worth repeating.

If all goes well, you should share everything, including settings for both installations.

There are two clarifications that I can think of, which can be useful for reasoning if this is not realistic:

  • you could probably share most of the installation of eclipse (the plugins and features directory, if not the config.ini and eclipse.ini files). If you cannot put both executables in the same directory, consider the -install and -configuration .
  • If you cannot perform any of these actions, you may need to work on two parallel workspaces. You can synchronize them with tools like rsync or even with distributed source control like Mercurial.
+1
source

I agree with bananeweizen.myopenid and add the following tip:

When creating build path entries, reference all external resources (e.g. jarfiles) using pathpath variables. This will allow you to move the .classpath file between environments (or even check it against the original control if you're the only developer) without running into pathname problems.

To reference a JARFile variable through a variable, go to the "Libraries" tab of the build path, delete any existing library reference, and click "Add Variable ...". You will need to define common variables, such as M2_REPO or LOCAL_LIBS, and you will need to make sure that these definitions are available in all your environments.

0
source

Perhaps the problem is related to capitalization. Be sure to first create a workspace in Ubuntu. This should eliminate any problems with uppercase file names.

0
source

All Articles