|Share project moves files [message #727459]
||Wed, 21 September 2011 11:14
| Bertin Kiekebosch
Registered: August 2011
I have some eclipse projects. After I shared the project the files are moved to an other location. From myWorkspace/myProject to git/myProject.|
Why is this done by GIT and how does Eclipse know where the files are now because there is almost an empty workspace left.
|Re: Share project moves files [message #728348 is a reply to message #727706]
||Fri, 23 September 2011 04:37
| Robin Rosenberg
Registered: July 2009
Matthias Sohn skrev 2011-09-21 22.56:|
> See  for explanations. If you still want to keep your project in the
> Eclipse workspace
> click "Use or create repository in parent folder of project" in the
> sharing wizard.
> Note: there is a plan to re-implement the sharing wizard to improve it's
> usability .
>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=356953
The motives in  aren't very relevant.
>The new Repository will consider the complete folder structure of the
>Eclipse workspace as (potential) content. This can result in
>performance issues, for example when calculating the changes before
>committing (which will scan the complete .metadata folder, for
>example); more often than not, the workspace will contain dead folders
>(e.g. deleted projects) which semantically are not relevant for EGit
>but can not be excluded easily.
When having repositories in the workspace, you normally don't create the
repository in the workspace root, but *below* the workspace. It
is possible to do it wrong, but the sharing wizard could alert you.
>The metadata (.git-) folder will be a child of the Eclipse Workspace.
>It is unclear whether this might cause unwanted folder traversals by
It is AFAIK clear that this is not an issue. I always have my projects
in my workspace, No problem whatsoever.
>You can easily destroy your Repository by destroying your Eclipse
Isn't that obvious? Destroying any directory will destroy its' content.
With the workspace you at least have a notion that a repository is used.
The global folder now gives me a ton of experimental projects not used.
Wit workspace storgage those projects only appear in the workspace where
I use them.
Of course I'm biased, since I'm used to having projects in the workspace.
Import from team projectset is inconsistent with the sharing wizard, so
nowadays unsuspecting users will wind up with some projects in the
workspace and some in the shared git directory.
Powered by FUDForum
. Page generated in 0.13578 seconds