Databases
StackOverflow2013
Postsdbo
PORecommended Eclipse EGit workflow
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORecommended Eclipse EGit workflow
    text
    copied!<p>Group,</p> <p>We use Borland Starteam as our source control system. I develop Java code and use Eclipse as my IDE. I recently started using EGit as my personal source control system and came up with the following workflow to streamline my dev work, which consists of checking out code, adding features, fixing bugs, testing, merging with the parent source in Star team (huge effort if lots of people have made changes in the meanwhile), build, test, and install. I want to use EGit to simplify the compile, merge and test process, while developing and also just before code install after big merges are made. This is what I have come up with. </p> <ol> <li>Create file system folders - 'Master' and 'Work' </li> <li>Check out fresh source folder structure from Starteam into 'Work'. </li> <li>Create Eclipse workspace called 'Work' and import Eclipse projects from 'Work' folder add those projects to an EGit repository.</li> <li>Add features/fix bugs while in 'Work' workspace. Test, etc. Create a patch when ready to install. Now its time to make the big merge, rebuild, test again.</li> <li>Check out fresh source from Starteam on the day of the install into 'Master' folder in the file system.</li> <li>Create Eclipse workspace 'Master' from source in 'Master' folder, import Eclipse projects and add those to a newly created EGit repository.</li> <li>Import patch into 'Master' workspace, perform merge. Fix compile errors, test, etc.</li> <li>Install.</li> </ol> <p>Is this workflow efficient? Are there more advanced features in EGit that would simply this any further?</p> <p>Thanks for any guidance. Ranjit</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload