Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search


< Virgo
Revision as of 09:38, 13 May 2015 by Unnamed Poltroon (Talk) (Virgo git Repositories: Adds Virgo root repository)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Virgo Components

The Virgo source code is organised into separate components which form a directed acyclic dependency graph. This is a layered architecture in which lower layers may provide function to higher layers but not vice versa.

It is important to understand the layering when making changes: changes to lower layers have a greater potential impact than changes to the higher layers.

To do: add a picture of the basic layering.

Virgo git Repositories

Virgo git repositories are hosted at and mirrored to github.

Each Virgo component resides in its own 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.

Note: some corporate firewalls do not permit the "git:" protocol, but you can substitute "http:" instead.

Short Name Description Anonymous: git clone Committer: git clone
apps Virgo-supplied applications git:// ssh://
artifact-repository Artifact repository git:// ssh://
bundlor Bundlor manifest generation tool git:// ssh://
documentation End-user documentation git:// ssh://
eclipse-mirror Handles mirroring of Eclipse p2 artifacts to Ivy repositories git:// ssh://
ide Eclipse IDE tooling git:// ssh://
kernel Core runtime git:// ssh://
kernel-system-verification-tests Kernel SVT tests git:// ssh://
kernel-tools Tools integration layer git:// ssh://
medic Diagnostics git:// ssh://
nano Nano git:// ssh://
packaging Virgo common packaging build git:// ssh://
performance-test Performance tests git:// ssh://
samples Sample Applications git:// ssh://
snaps Modular web UI git:// ssh://
system-verification-tests SVT tests git:// ssh://
test Test framework git:// ssh://
util utilities git:// ssh://
virgo-build Ant/Ivy based build system git:// ssh://
web Web integration layer git:// ssh://
root Virgo root repository git:// ssh://

Virgo's project web site resides in the following git repository.

Short Name Description Anonymous: git clone Committer: git clone
web site Virgo project web site git:// ssh://

Virgo's sister projects, from Gemini, resides in the following git repositories.

Short Name Description Anonymous: git clone Committer: git clone
gemini-web-container Gemini web container git:// ssh://
gemini-management Gemini management git:// ssh://
gemini-blueprint Gemini Blueprint git:// ssh://

Source Organisation

A typical git repository is organised into the following files and directories:

build-xxx/                         // top-level build directory                   // properties substituted during build
build.versions                     // dependency version properties         // 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                        // Bundlor template

How to Add new woven project to Virgo

Generally all kernel projects and up stream projects are woven to add supportability features. In order to add a new Virgo project you need to create a Java project with the structure described above. The Spring tooling is only necessary if your projects utilizes Spring at runtime. When your project is ready you need to add a weaving dependencies so there won't be errors during the ant build time weaving process.

The dependency must be places in the project's ivy.xml. Here it is: <dependency org="org.aspectj" name="" rev="${org.aspectj}" conf="compile->runtime"/>

And you're done. Now project will be woven like the rest of the kernel projects.

How to Add a 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>
>initrepo /gitroot/virgo/org.eclipse.virgo.<reponame>.git
<log out e.g. using Ctrl-D>

2. Clone the new repository:

>git clone ssh://<committer_id><reponame>.git <repo dir>

3. Create the directories of the new repository and any .gitignore file. For example:

>cd <repo dir>
>cp <source dir>/.gitignore .
>cp -r <source dir>/o* .
>cp -r <source dir>/b* .
Make sure you get all the files -- some of them may not fall into these patterns.

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:// 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 (may require project lead privileges).

>rsync .git/description <committer-id><reponame>.git/description

8. Add the new repository to the table above.

9. Use the Foundation Portal to add the new repository to the list of source repositories in the project metadata. In particular, this should cause the repository to be mirrored on github.

10. Don't forget to create Hudson build jobs, if you need them, and close any bug which was tracking the creation of the new repository.


Sometimes it is necessary to delve into the origins of a particular piece of code. Virgo (and Gemini Web Container) derived from SpringSource dm Server. If you want to start digging, please note that the original source is licensed partly under the GPL v3 and partly under the Apache License v2. The original git repositories are available on in the dm Server and OSGi Web Container projects. The intermediate repositories used to prepare the donation to Eclipse are also on in the Virgo and Gemini projects.

In order to protect Eclipse users from accessing non-Eclipse licensed code, the history was trimmed from the Virgo (and Gemini Web Container) repositories. However the commit log message of the first commit to each Eclipse repository notes the SHA of the commit in the intermediate repository from which it was copied. Note also that some samples were not contributed because of uncertain authorship, so a few dm Server repositories do not correspond to any Virgo repository.

Back to the top