Difference between revisions of "Gemini/mvn"

From Eclipsepedia

Jump to: navigation, search
(Example Dependency Definition)
(forget git)
 
Line 34: Line 34:
 
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, git can be used to back out a disastrous unzip attempt.
+
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.

Latest revision as of 10:53, 26 February 2013

Contents

[edit] 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.

[edit] Repository Definition

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

[edit] Example Dependency Definition

<dependency>
    <groupId>org.eclipse.gemini</groupId>
    <artifactId>org.eclipse.gemini.web</artifactId>
    <version>2.2.0.RELEASE</version>
</dependency>

[edit] 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.