Jump to: navigation, search

Difference between revisions of "Gemini/mvn"

(Adding Artefacts to the Repository)
Line 14: Line 14:
 
Committers may access this by ssh'ing to build.eclipse.org.
 
Committers may access this by ssh'ing to build.eclipse.org.
  
The simplest way of updating the Maven repository is to create a local Maven repository, upload this as a zip file and then unzip it in the mvn directory above. Since mistakes can happen, the '''mvn directory is a git repository'''. Committers should therefore  add and commit their changes as usual in git. This way, it is easy to back out a disastrous unzipping using git.
+
The simplest way of updating the Maven repository is to create a local Maven repository, upload this as a zip file and then unzip it in the mvn directory above. Since mistakes can happen, the '''mvn directory is a git repository'''. Committers should therefore  add and commit their changes as usual in git. This way, git can be used to back out a disastrous unzip attempt.

Revision as of 10:29, 5 December 2012

Gemini Maven Repository

The Gemini subprojects contribute to a shared Maven repository at:

Maven repository definition TBD

All Gemini subprojects have Maven coordinates with a group id of org.eclipse.gemini.

Adding Artefacts to the Repository

The repository is stored on the download server at:

/home/data/httpd/download.eclipse.org/gemini/mvn

Committers may access this by ssh'ing to build.eclipse.org.

The simplest way of updating the Maven repository is to create a local Maven repository, upload this as a zip file and then unzip it in the mvn directory above. Since mistakes can happen, the mvn directory is a git repository. Committers should therefore add and commit their changes as usual in git. This way, git can be used to back out a disastrous unzip attempt.