The repository might be a fork we have created for our own use or it might be a Joomla project (CMS or Platform) or someone else's project. In any case, we follow the same three steps: Clone the remote repository into a local Git repository. Create a new PHP project in our Eclipse workspace. Share the project. Eclipse EGit is the Git integration for Eclipse. Git is a distributed SCM, which means every developer has a full copy of all history of every revision of the code, making queries against the history very fast and versatile. The EGit project is implementing Eclipse tooling for the JGit Java implementation of Git.
I've googled all day time and now there's so many Git questions, it's difficult to find anything about my real query, which is this.
I have got a nearby Git database arranged up. I can pull a formerly dedicated project into Eclipse (via 'transfer.'), but when I do, the project offers no association with that Git database. The Eclipse project is usually really a hyperlink to the Git work area, so I'm functioning with the correct documents, but since Eclipse can be ignorant of the link, I can't make use of any of the team functions on that project.
I recognize I can then team-gt;share the project and it will duplicate it somewhere else, but I don't see the point now there (and it will most likely split the initial database as Eclipse will move the data files from the previous place to the brand-new).
In CVS and SVN you 'checkout' and you obtain a copy and the organization is instantly produced with the repository you obtained the document from. I'meters not viewing how to perform that with Git in Eclipse.
karel9,7731111 yellow metal badges3535 silver precious metal badges4040 bronze badges
StuStu69944 magic badges1010 silver badges2424 bronze badges
3 Answers
After very much putzing around, I finally figured it out.As soon as you import the project from the git database into the eclipse work area, you then team-gt;talk about it back to the same database and it will connect it.Not really certainly why this is definitely a two stage process but that's how I made it proceed. Maybe there's a simpler way, but I haven't discovered it however.
StuStu69944 yellow metal badges1010 silver precious metal badges2424 bronze badges
I got this concern as nicely.And I'm not sure if you are usually going about points the exact same method I did. But just to compare, I brought in a project from GitHub and utilized the 'New Task Sorcerer' when caused by Eclipse. This sorcerer requires me to select a listing for the project. And if the directory site selected there is different from the directory website that the Import Wizard utilized to import the git repo, of program, the project is definitely not linked.
Instead of going about the team-gt;share technique, upon importing the project (with the New Project Wizard) I made certain that the New Task Wizard used the exact same directory site as the Transfer Wizard (the one the repo brought in uses).
If you are able to instead Import Existing Tasks, for some reason it connects everything automatically without opening the New Project Sorcerer.
I suppose the New Task Wizard provides one unnecessary stage in this specific use case (since we can believe you mean for the brought in repo to become automatically connected.
Simply an remark.
Jeremy Gary the gadget guyJeremy Gary the gadget guy
Right click gt; Import gt; Tasks from Git gt; Existing local repository
Andy CarterAndy Carter