Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Gemini/mvn"
< Gemini
m (→Repository Definition) |
|||
| Line 10: | Line 10: | ||
<pre> | <pre> | ||
| − | + | <repository> | |
| + | <id>eclipse-gemini</id> | ||
| + | <name>Eclipse Gemini Maven repository</name> | ||
| + | <url></url> | ||
| + | </repository> | ||
</pre> | </pre> | ||
Revision as of 10:39, 18 December 2012
Contents
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></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.