Jump to: navigation, search

Difference between revisions of "Gemini/mvn"

(Gemini Maven Repository)
Line 5: Line 5:
 
<pre>http://download.eclipse.org/gemini/mvn/</pre>
 
<pre>http://download.eclipse.org/gemini/mvn/</pre>
  
All Gemini subprojects should have Maven coordinates with a group id of org.eclipse.gemini.  
+
All Gemini subprojects should have Maven coordinates with a group id of org.eclipse.gemini.
 +
 
 +
== Repository Definition ==
 +
 
 +
<pre>
 +
to be supplied
 +
</pre>
 +
 
 +
== Example Dependency Definition ==
 +
 
 +
<pre>
 +
to be supplied
 +
</pre>
  
 
== Adding Artefacts to the Repository ==
 
== Adding Artefacts to the Repository ==

Revision as of 10:37, 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

to be supplied

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.