The EclipseLink project currently produces a maven repository for its releases

−

The use of the Eclipse mirrors for Maven repositories has been reported to cause varying issues from artifacts being reported as unavailable to local maven repository corruption. Therefore, instead of using the mirrored download URL:

it is recommended that you use the unmirrored URL to directly access the EclipseLink Maven repository on the Eclipse download site instead:

+

−

* http://download.eclipse.org/rt/eclipselink/maven.repo

+

−

''Note: because of the way these repositories are maintained at Eclipse, you will not be able to see into them by clicking on these links. If you have issues actually running a maven build, please report those issue via either the users mailing list or the forum. (If you are using Nexus, please see below before doing that)''

+

If you have any questions about using it, or experience problems, please let us know on our users mailing list or forum.

−

== Basic Example POM ==

+

== Configuring your pom.xml ==

−

To help users diagnose Maven issues, we have created a basic POM that simply establishes EclipseLink dependencies (currenly using the 2.4.0 release). Executing it will verify your connection to the repository. Alternate Repository URLs are discussed. The POM can be found [[http://www.eclipse.org/downloads/download.php?file=/rt/eclipselink/pom.xml | here]].

+

To help users diagnose Maven issues, we have created a basic POM that simply establishes EclipseLink dependencies (currenly using the 2.4.0 release). Executing it will verify your connection to the repository. Alternate Repository URLs are discussed. The POM can be found [[http://www.eclipse.org/downloads/download.php?file=/rt/eclipselink/pom.xml here]].

−

If you have any questions about using it, or experience problems, please let us know on our users mailing list or forum.

+

=== <repository> ===

−

== Proxying using Repository Managers (Nexus et al.) ==

+

Within your pom.xml you will need to specify the EclipseLink repository using:

+

<source lang="xml">

+

<repository>

+

<id>EclipseLink</id>

+

<url>http://download.eclipse.org/rt/eclipselink/maven.repo</url>

+

</repository>

+

</source>

−

We appreciate your attempt to proxy the EclipseLink repository using a repository manager like Nexus and others. It reduces load from our servers and speeds up your local builds by reducing traffic over the web. There is work in progress to publish our releases of EclipseLink on the Eclipse Foundation's Nexus instance at http://maven.eclipse.org/nexus, but this is not finally done yet. Currently we only publish to a P2 instance directly, which is not trivial to proxy using a Maven repository manager due to technical differences, but it is possible with some helpful information:

+

== <dependencies> ==

−

=== Using Nexus Professional ===

+

The artifacts can then be added to you pom as follows. The complete list of available artifacts and their usage is below.

−

Nexus Professional natively can proxy P2 repositories. Just provide the address "http://download.eclipse.org/rt/eclipselink/maven.repo/" and set the proxy type to P4. See http://www.sonatype.com/books/nexus-book/reference/p2-sect-intro.html for more details.

+

<source lang="xml">

+

<dependency>\

+

<groupId>org.eclipse.persistence</groupId>

+

<artifactId>{artifact}</artifactId>

+

<version>{version}</version>

+

<scope>compile</scope>

+

</dependency>

+

</source>

−

=== Using Nexus Open Source ===

+

The following are the primary artifacts. All listed dependencies are also included in this repository.

−

+

−

Since Nexus Open Source cannot natively proxy P2 repositories, you have to take a bit more care:

You will be able to download artifacts using these seetings (which is what you primarily want), but note that you will neither be able to search nor browse artifacts that have not already been downloaded into the Nexus cache. The reason is that without native P2 support, Nexus read an index or list of artifacts found in the remote P2 repository. As this is only a secondary use of a repository manager, we hope you are not too disappointed. Remember, this will work as soon as we moved over to Eclipse's Nexus instance.

+

−

+

−

See http://www.sonatype.com/books/nexus-book/reference/config-sect-new-repo.html#id3046241 for more detail.

| EclipseLink JPA (OSGi bundle): Use this artifact if you only want EclipseLink's JPA capabilities for relational databases. If accessing an Oracle database then you will also want the '''org.eclipse.persistence.oracle''' artifact.

* Core (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

* Antlr (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

* Asm (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

+

−

==== SDO Only ====

+

−

* SDO

+

For the available EclipseLink release versions please refer to the [http://www.eclipse.org/eclipselink/releases/ releases page]. It is the 3 digit number that is used. For access to nightly or milestone builds please see [[EclipseLink/Maven/NightlyMilestones]]

−

* MOXy

+

−

* Core (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

* Antlr (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

* Asm (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

==== Core Only ====

+

== Sample pom.xml ==

−

* Core (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

The following pom.xml is from an EclipseLink example that uses JPA to access a MySQL database and leverages JUnit for testing.

−

* Antlr (starting in 2.0.0 should be retrieved by maven dependency mechanism)

+

−

* Asm (starting in 2.0.0 should be retrieved by maven dependency mechanism)

If you have any questions about using it, or experience problems, please let us know on our users mailing list or forum.

Configuring your pom.xml

To help users diagnose Maven issues, we have created a basic POM that simply establishes EclipseLink dependencies (currenly using the 2.4.0 release). Executing it will verify your connection to the repository. Alternate Repository URLs are discussed. The POM can be found [here].

<repository>

Within your pom.xml you will need to specify the EclipseLink repository using:

EclipseLink JPA (OSGi bundle): Use this artifact if you only want EclipseLink's JPA capabilities for relational databases. If accessing an Oracle database then you will also want the org.eclipse.persistence.oracle artifact.