![]() ![]() #Eclipse java git open in terminal codeThat, however, has the effect of putting all the source code outside of the Eclipse workspace, which is confusing. Researching this, the stock advice seems to be to set up the repository outside of the Eclipse project. If they don't know git init and git clone (origin) then I'm sorry, they do not know Git, they should learn this first (along with push, pull, commit, status, fetch). If I ask them to use the command line, they will never do it. To me it sounds like your students lack an understanding of the fundamentals of IDEs and Git. So does anyone have a setup for Eclipse and eGit that successfully puts the entire project into version control, and is not confusing for students? And that allows the project to correctly import into Eclipse? This, I think, would be less confusing to students, but when I try that, I get all kinds of nasty warning messages. The other method would be to put the repository (and. Worse yet, I can't then import the project correctly into another Eclipse environment. ![]() I want them to use the eGit plugin because if I ask them to use the command line, they will never do it. What I want to do is have them put entire Eclipse projects (without the binaries) on GitHub. I want them to use Eclipse with Git, but I am struggling myself to find a way to set it up that would make sense to a student. My students struggle terribly with Eclipse, and with any form of version control. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |