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

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

Line 12:

Line 14:

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

−

=== <repository> ===

+

=== Repositories ===

+

+

Within your pom.xml you will need to specify the EclipseLink repository (within <repositories>).

+

+

==== oss.sonatype.org: 2.4.2 and Later ====

+

+

The EclipseLink project has switched to publishing its builds through oss.sonatype org during the 2.4.2/2.5.0 development. The staging repo will provide access to SNAPSHOT and named milestone and release candidate builds. To access these use:

+

+

<source lang="xml">

+

<repository>

+

<id>oss.sonatype.org</id>

+

<name>OSS Sonatype Staging</name>

+

<url>https://oss.sonatype.org/content/groups/staging</url>

+

</repository>

+

</source>

+

+

When the 2.4.2 and above releases are finalized they will be published to [http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.eclipse.persistence%22 Maven Central] where no additional repository configuration will be required.

+

+

==== Custom Repo: 2.4 and Earlier ====

+

+

For builds prior to EclipseLink 2.5 please use:

−

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

<source lang="xml">

<source lang="xml">

<repository>

<repository>

Line 27:

Line 48:

<source lang="xml">

<source lang="xml">

−

<dependency>\

+

<dependency>

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

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

<artifactId>{artifact}</artifactId>

<artifactId>{artifact}</artifactId>

Line 103:

Line 124:

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]]

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]]

−

== Sample pom.xml ==

+

== Sample pom.xml (Staging) ==

−

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

+

The following pom.xml illustrates access the EclipseLink 2.5.0-RC1 from our staging repository.

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

Repositories

Within your pom.xml you will need to specify the EclipseLink repository (within <repositories>).

oss.sonatype.org: 2.4.2 and Later

The EclipseLink project has switched to publishing its builds through oss.sonatype org during the 2.4.2/2.5.0 development. The staging repo will provide access to SNAPSHOT and named milestone and release candidate builds. To access these use:

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.