| Working with Egit and non-Eclipse projects [message #897341] |
Mon, 23 July 2012 16:25  |
 Jason Litton
Messages: 3
Registered: July 2012 |
Junior Member |
|
|
I'd like to import a non-Eclipse project and work with it in Eclipse, but I keep getting blocked by Egit. I'm wondering if the following workflow is possible without leaving Eclipse and, if so, how.
1. Clone a git repo for a non-Eclipse project
2. Fetch a gerrit branch for the project above. The gerrit branch also lacks a .project file.
3. Merge the two branches and resolve conflicts.
I've tried several strategies:
A. Do step 1 above -> New project -> uncheck 'use default' -> point project to git location -> when project is added, share project to git repo. This hooks the project into the git repo well. I can branch from there, change code, commit and push. However, I cannot fecth and merge the gerrit branch if I do that.
B. Fetch each as a separate repo, then open different projects for each. This doesn't work because there doesn't seem to be a way to merge two projects.
C. Try to clone the original repo, make a branch and then merge without making a project. If the merge has conflicts, there's no way to create an Eclipse project and I have to go to a different editor to resolve conflicts.
So, is there a way accomplish this using ONLY Egit? I know I can do command line git and a different editor, but I'd like to be able to do it from within Eclipse.
Any pointers would be greatly appreciated. Thanks.
|
|
|
|
| Re: Working with Egit and non-Eclipse projects [message #901337 is a reply to message #901336] |
Fri, 10 August 2012 21:52  |
Jason Litton
Messages: 3
Registered: July 2012 |
Junior Member |
|
|
1) Correct. The project itself was not created in Eclipse. Some people who work on the project use Eclipse, but some do not. The actual project is not required to use Eclipse, but I, as a developer, would like to use Eclipse for my editing and debugging.
2) There is a general public repository for the project and a separate gerrit server for commits. When a patch has been approved from gerrit, it goes to the general public repository. So when I say "Gerrit branch" I mean a branch of the project that is awaiting review on that gerrit server.
3) A good "for instance" would be Linux Kernel development. They use git and gerrit, but do not necessarily need to be developed in Eclipse. Some developers would edit through vim, some through notepad, some on Eclipse. I've also got developers working on the coreboot project, which has the same drawbacks. Eclipse is useful but not required to be a developer on these projects, so it cannot be guaranteed that every git or gerrit pull will contain .project data.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02019 seconds
] 
Search
Help
Register
Login
Home
