Jump to: navigation, search

Difference between revisions of "Gemini/mvn"

m (Repository Definition)
(Repository Definition)
Line 13: Line 13:
 
       <id>eclipse-gemini</id>
 
       <id>eclipse-gemini</id>
 
       <name>Eclipse Gemini Maven repository</name>
 
       <name>Eclipse Gemini Maven repository</name>
       <url></url>
+
       <url>http://download.eclipse.org/gemini/mvn/</url>
 
</repository>
 
</repository>
 
</pre>
 
</pre>

Revision as of 10:39, 18 December 2012

Gemini Maven Repository

The Gemini subprojects contribute to a shared Maven repository at:

http://download.eclipse.org/gemini/mvn/

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

Repository Definition

<repository>
      <id>eclipse-gemini</id>
      <name>Eclipse Gemini Maven repository</name>
      <url>http://download.eclipse.org/gemini/mvn/</url>
</repository>

Example Dependency Definition

to be supplied

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.