Jump to: navigation, search

Difference between revisions of "DTP Source Code Repository"

(Resources for getting familiarized with Git)
m (Resources for getting familiarized with Git)
Line 52: Line 52:
* [http://progit.org/book/ Pro Git book] - especially chapter 3
* [http://progit.org/book/ Pro Git book] - especially chapter 3
* http://wiki.eclipse.org/Git/Migrating_to_Git
* http://wiki.eclipse.org/Git/Migrating_to_Git
* [[Platform-releng/Git_Workflows]] from Paul for migrators from CVS
* [[Platform-releng/Git_Workflows]] by Paul Webster for migrators from CVS
* [http://tom.preston-werner.com/2009/05/19/the-git-parable.html The Git Parable]
* [http://tom.preston-werner.com/2009/05/19/the-git-parable.html The Git Parable]
* [[Git]] page by Denis Roy (Eclipse infrastructure, Legal stuff, pulling from external repos)
* [[Git]] page by Denis Roy (Eclipse infrastructure, Legal stuff, pulling from external repos)

Revision as of 18:49, 14 July 2011

Back to DTP Main Page

Migration from CVS to Git

DTP source code repository has been maintained on CVS since the beginning of the project. After the Indigo release (DTP 1.9), the DTP project is planning to migrate our source code repository from Eclipse CVS to Git. This is in line with the overall direction of Eclipse projects. We also want to take the opportunity to refine the source code organization and clean up obsolete plug-ins, as part of the migration.

We are essentially migrating the DTP CVS Head branch to Git, and it will include the history in CVS. Starting from DTP 1.9.1 (Indigo SR1 release) and on, builds will be made from the Eclipse Git source code repositories. If there is ever a need to build DTP 1.9 or older version, it should still grab the source from corresponding CVS branches.

We are not currently doing any nightly build for the 1.9.1 release. It will resume when the Git migration is completed.

DTP Git Repository Organization

Separate Git repository will be created for each DTP sub-project. The main guideline used for the repository split is to group those highly-related projects that are likely maintained by the same set of committers.

Below are the list of separate DTP Git repositories. See the spreadsheet for the proposed directory structure and content in each Git repository. Note that obsolete or archived plug-in projects will not be migrated, and are thus not included in the Git repositories.

Separate Git source repositories for each sub-project and enablement groupings

  • org.eclipse.datatools.connectivity.git
  • org.eclipse.datatools.modelbase.git
  • org.eclipse.datatools.sqltools.git
  • org.eclipse.datatools.enablement.<vendor>.git

            where <vendor> are: hsqldb, ibm, ingres, msft, mysql, oda, oracle, postgresql, sap, sqlite, sybase

  • org.eclipse.datatools.enablement.general.git -- contains non-vendor specific enablement plugin projects
  • org.eclipse.datatools.incubator.git

Each of the above source repositories contains the following sub-folders, if content exists:

  • plugins/  : contains source plug-in projects
  • releng/  : contains map file of the source plug-in projects
  • tests/  : contains unit test plug-ins
  • examples/ : exemplary implementation projects

Additional separate Git repositories for non-source projects

  • org.eclipse.datatools.build.git
  • org.eclipse.datatools.doc.git
  • org.eclipse.datatools.nl.git

Resources for getting familiarized with Git

Some Useful EGit/Git Documentation

Temporary Test Git Repositories

We have created a few temporary test Git repositories on github.com. Note that the directory structures found in these test repos are not the proposed ones. (See the spreadsheet attached above for the proposed directory structures.)

To write (e.g. push) to the DTP test remote repos on github, it will need a password: Actuate2011

Browsing Remote Git Repositories

To browse the content of a remote Git repo, use a web browser with the remote repo URL, e.g.