Jump to: navigation, search

Difference between revisions of "Gemini/mvn"

(New page: = Gemini Maven Repository = The Gemini subprojects contribute to a shared Maven repository at: <pre>Maven repository definition TBD</pre> All Gemini subprojects have Maven coordinates ...)
 
Line 5: Line 5:
 
<pre>Maven repository definition TBD</pre>
 
<pre>Maven repository definition TBD</pre>
  
All Gemini subprojects have Maven coordinates with a group id of <pre>org.eclipse.gemini</pre>.  
+
All Gemini subprojects have Maven coordinates with a group id of org.eclipse.gemini.  
  
 
== Adding Artefacts to the Repository ==
 
== Adding Artefacts to the Repository ==

Revision as of 08:17, 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, it is easy to back out a disastrous unzipping using git.