Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Gemini/mvn"

(Adding Artefacts to the Repository)
m
 
(6 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
The Gemini subprojects contribute to a shared Maven repository at:
 
The Gemini subprojects contribute to a shared Maven repository at:
  
<pre>Maven repository definition TBD</pre>
+
<pre>http://download.eclipse.org/gemini/mvn/</pre>
  
All Gemini subprojects 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>
 +
<repository>
 +
      <id>eclipse-gemini</id>
 +
      <name>Eclipse Gemini Maven repository</name>
 +
      <url>http://download.eclipse.org/gemini/mvn/</url>
 +
</repository>
 +
</pre>
 +
 
 +
== Example Dependency Definition ==
 +
 
 +
<pre>
 +
<dependency>
 +
    <groupId>org.eclipse.gemini</groupId>
 +
    <artifactId>org.eclipse.gemini.web</artifactId>
 +
    <version>2.2.0.RELEASE</version>
 +
</dependency>
 +
</pre>
  
 
== Adding Artefacts to the Repository ==
 
== Adding Artefacts to the Repository ==
  
The repository is stored on the download server at:
+
The repository is stored on the download server at, see https://wiki.eclipse.org/IT_Infrastructure_Doc
 
<pre>/home/data/httpd/download.eclipse.org/gemini/mvn</pre>
 
<pre>/home/data/httpd/download.eclipse.org/gemini/mvn</pre>
  
 
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 18:36, 21 March 2016

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

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

Adding Artefacts to the Repository

The repository is stored on the download server at, see https://wiki.eclipse.org/IT_Infrastructure_Doc

/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.

Back to the top