Home/ Questions/Q 6775175
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T15:52:32+00:00

I use Linux as primary operating system and I also have to work on

  • 0

I use Linux as primary operating system and I also have to work on a Windows virtual machine with Eclipse 3.7.

We’re working with subversion but with Linux I’m happily using git-svn with Emacs+magit, which works great.
So I would like to be able to work on the same code from both OS, and only do the real version control management on Linux.

So I had the following thought:
1. share the directory with virtualbox
2. create the projects pointing to the shared directory

Well that doesn’t work, because the dumb thing wants to copy everything.
So I tried to use virtual folders which seemed a good idea, but now some scripts are badly failing because they don’t find the hard-coded paths.

So I don’t know anymore what to try, any idea?

EDIT:
My last attempt in the last edit would not work, so I have a simpler question.
Given a git/svn/whatever repository checkout, why can’t I simply tell to Eclipse create a project there without touching the files?

Is it so hard for Eclipse to create it’s .project in that position?
And since there is clearly no “supported” way to do it, is there maybe any workaround?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Eclipse modifies and compiles source in its workspace. The first level of the workspace is the project directories, + a .metadata which is local only to that workspace instance. Traditionally, the workspace contains the projects it works on.

    Eclipse also supports 2 linked modes. In one, when you create the project in the workspace you give it an absolute path to somewhere else on the file system. This is handy if you have eclipse projects in a git repo, for example.

    In the other mode, you create the project in your workspace locally. Then you link your folders (source, resources, whatever) to somewhere else on the filesystem. This is useful for projects that don’t want to save the eclipse specific files (.project, .classpath, etc) in their SCM.

    You have to create a different workspace on each OS (there’s no way around that). But you could create the projects in each workspace and link to the common location (I don’t recommend it, but it would be do-able).

    • 0