|
|
|
| Re: Exit from Eclipse Git [message #1856893 is a reply to message #1856892] |
Sat, 07 January 2023 18:25   |
 David M. Karr
Messages: 801
Registered: July 2009 |
Senior Member |
|
|
What do you actually need or want to do? What do you mean by "get out of GIT"?
In general, you should have a location on disk where your git repositories live, I typically put them all in ~/git . Your Eclipse workspace will be in a different place. I create one workspace for each Eclipse distribution. You import from git repositories into your eclipse workspace, although what gets imported into the workspace is really just metadata about the projects, it doesn't import the actual files stored in your git repository.
If you want to stop using Git for some odd reason, then I guess you could delete the Eclipse project from within eclipse, and NOT checking the box for deleting the "project contents", which will be in the git repository. Then, you should copy the current contents of the git repository to some other place, and then delete the ".git" directory in the destination. Then, back in Eclipse, you can import "Existing Projects into Workspace" or "File System", specifying the location you copied the git repository to.
Frankly, you should simply get used to git and get more familiar with it.
|
|
|
|
|
|
| Re: Exit from Eclipse Git [message #1856898 is a reply to message #1856895] |
Sun, 08 January 2023 13:54 |
Thomas Wolf
Messages: 576
Registered: August 2016 |
Senior Member |
|
|
David M. Karr wrote on Sat, 07 January 2023 19:43When Eclipse imports from a remote location, it creates a handful of "dot files" in the root directory of the repository, like ".project", ".classpath", and ".settings", which are not in the ".git" directory. If you preserve those files, you'll preserve some preferences and project settings. Not that this helps you right now, but note that those dot files should generally NOT be checked into git, because Eclipse tends to modify them (obviously).
This is not correct. If the Eclipse project is in the git working tree, then that is also where the .project/.classpath/.settings are. (Of course a project is not inside the .git directory. You should never work there directly, that directory is managed by git.) Other plug-in specific data is typically stored in the Eclipse workspace, inside the .metadata sub-directory.
If you keep the place where you store git repository clones separate from the Eclipse workspace, that .metadata directory is never in any git repository, and you don't have to worry about it. If the Eclipse workspace directory is equal to the git working tree directory (or a subdirectory thereof), then you might want to ensure via .gitignore that the files in .metadata directory are ignored and never checked in.
The second part of that quote is highly questionable. That may be what you do, but in my environments, it would be patently false. Do check in .project/.classpath/.settings. That way all Eclipse users who check out the code automatically get the right setup. Eclipse normally does not modify them once created, and if so, you probably also want to check in these modifications so that other users get them, too.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03575 seconds
] 
Search
Help
Register
Login
Home
