Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Virgo/Source"
| Line 1: | Line 1: | ||
{{Virgo}} | {{Virgo}} | ||
| + | |||
= Virgo git Repositories = | = Virgo git Repositories = | ||
| Line 135: | Line 136: | ||
template.mf // Bundlor template | template.mf // Bundlor template | ||
</pre> | </pre> | ||
| + | = How to add another git repository to Virgo = | ||
| + | |||
| + | While this information is mainly of use while the Virgo repositories are initially being populated, it may be useful later. It says how to trace back from Virgo to its origins, how to update a repository description, and what files to copy when a new repository is added. | ||
| + | |||
| + | 1. Add the new repository to the git server (may require project lead privileges): | ||
| + | <pre>>ssh <committer_id>@git.eclipse.org | ||
| + | >cd /gitroot/virgo | ||
| + | >initrepo org.eclipse.virgo.<reponame>.git | ||
| + | <log out e.g. using Ctrl-D> | ||
| + | </pre> | ||
| + | 2. Clone the new repository: | ||
| + | <pre>>git clone ssh://<committer_id>@git.eclipse.org/gitroot/virgo/org.eclipse.virgo.<reponame>.git <repo dir> | ||
| + | </pre> | ||
| + | 3. Create the directories of the new repository and any .gitignore file. For example: | ||
| + | <pre>>cp <source dir>/.gitignore org.eclipse.virgo.<reponame>/. | ||
| + | >cp <source dir>/o* org.eclipse.virgo.<reponame>/. | ||
| + | >cp <source dir>/b* org.eclipse.virgo.<reponame>/. | ||
| + | </pre> | ||
| + | 4. If you are creating the new repository from an existing git repository, tag the existing repository and make a note of the tagged commit SHA. | ||
| + | <pre>>cd <source dir> | ||
| + | >git tag Virgo-checkin | ||
| + | >git push origin master --tags | ||
| + | >cd <repo dir> | ||
| + | </pre> | ||
| + | 5. Add a submodule for Virgo build. | ||
| + | <pre>>git submodule add git://git.eclipse.org/gitroot/virgo/org.eclipse.virgo.virgo-build.git virgo-build | ||
| + | </pre> | ||
| + | 6. Stage all the above changes and push to master. | ||
| + | <pre>>git add . | ||
| + | > git commit -m "initial checkin from <existing repository> commit <tagged commit SHA>" | ||
| + | >git push origin master | ||
| + | </pre> | ||
| + | 7. Edit .git/description, making sure the file is a single line ending in a newline, and rsynch this. | ||
| + | <pre>>rsync .git/description <committer-id>@git.eclipse.org:/gitroot/virgo/org.eclipse.virgo.<reponame>.git/description | ||
| + | </pre> | ||
| + | 8. Add the new repository to the table above. | ||
| + | |||
[[Category:Virgo]] [[Category:EclipseRT]] | [[Category:Virgo]] [[Category:EclipseRT]] | ||
Revision as of 03:56, 5 May 2010
Virgo git Repositories
The Virgo source code is organised into separate components each stored in a git repository. The Build tab details how to clone and build these components, but if you want a quick peek at the source code, follow the Short Name links in the table.
Source Organisation
A typical git repository is organised into the following files and directories:
build-xxx/ // top-level build directory build.properties // properties substituted during build build.versions // dependency version properties org.eclipse.virgo.xxx.y.z/ // a project ... // more projects virgo-build/ // git submodule
Each project is organised into the following files and directories:
.classpath // Eclipse build class path .project // Eclipse project metadata .settings/ // Settings .springBeans // Spring tooling metadata build.xml // Ant build instructions ivy.xml // Ivy build dependencies src/main/java/ // Runtime source src/main/resources/ // Runtime resources src/test/java/ // Unit/integration test source src/test/resources/ // Unit/integration test resources template.mf // Bundlor template
How to add another git repository to Virgo
While this information is mainly of use while the Virgo repositories are initially being populated, it may be useful later. It says how to trace back from Virgo to its origins, how to update a repository description, and what files to copy when a new repository is added.
1. Add the new repository to the git server (may require project lead privileges):
>ssh <committer_id>@git.eclipse.org >cd /gitroot/virgo >initrepo org.eclipse.virgo.<reponame>.git <log out e.g. using Ctrl-D>
2. Clone the new repository:
>git clone ssh://<committer_id>@git.eclipse.org/gitroot/virgo/org.eclipse.virgo.<reponame>.git <repo dir>
3. Create the directories of the new repository and any .gitignore file. For example:
>cp <source dir>/.gitignore org.eclipse.virgo.<reponame>/. >cp <source dir>/o* org.eclipse.virgo.<reponame>/. >cp <source dir>/b* org.eclipse.virgo.<reponame>/.
4. If you are creating the new repository from an existing git repository, tag the existing repository and make a note of the tagged commit SHA.
>cd <source dir> >git tag Virgo-checkin >git push origin master --tags >cd <repo dir>
5. Add a submodule for Virgo build.
>git submodule add git://git.eclipse.org/gitroot/virgo/org.eclipse.virgo.virgo-build.git virgo-build
6. Stage all the above changes and push to master.
>git add . > git commit -m "initial checkin from <existing repository> commit <tagged commit SHA>" >git push origin master
7. Edit .git/description, making sure the file is a single line ending in a newline, and rsynch this.
>rsync .git/description <committer-id>@git.eclipse.org:/gitroot/virgo/org.eclipse.virgo.<reponame>.git/description
8. Add the new repository to the table above.