JPA 2.0 API maven artifact

Question

I am using JPA 2.0 and my persistence provider is Hibernate; however, I'd like to just include a standard API from javax, but in central, there is no 2.0 artifact. I am currently using the Hibernate JPA 2.0 artifact, but I'd like to use something more standard.

Is this possible?

Thanks,

Walter

score 18 · Accepted Answer · edited Mar 29 '12 at 19:28

18

I am currently using the Hibernate JPA 2.0 artifact, but I'd like to use something more standard

There is still no javax.persistence:persistence-api:jar:2.0 artifact from Sun/Oracle. Either use the full javax:javaee-api:jar:6.0 artifact if you want something from Sun/Oracle... or just stick with the interfaces provided by Hibernate, EclipseLink, OpenJPA, etc.

edited Mar 29 '12 at 19:28

Laurent Pireyn

6,627
1
28
39

answered Oct 09 '10 at 00:13

Pascal Thivent

549,808
132
1,049
1,115

Is this still the case as of November 2010? – HDave Nov 18 '10 at 17:34
There's a typo: you have 'javaeee-api' (note the 3 e's), should be 'javaee-api' – Miguel Ping Nov 29 '11 at 11:20
5

Seems this is still the case here in January 2012...what gives? – HDave Jan 03 '12 at 18:59
Please see my answer below, with details about an official Oracle jar containing the JPA 2.0 API interfaces. – devdanke Jun 22 '15 at 01:37

rmuller · Answer 2 · 2020-06-06T17:03:55.817

Currently (Q1 2020) the default artifact is

<dependency>
  <groupId>jakarta.persistence</groupId>
  <artifactId>jakarta.persistence-api</artifactId>
  <version>2.2.3</version>
</dependency>

An older artifact of javax.persistence-api is also available at maven central, but is superseded by the jakarta version.

<dependency>
  <groupId>javax.persistence</groupId>
  <artifactId>javax.persistence-api</artifactId>
  <version>2.2</version>
</dependency>

The code is maintained in this github repo.

score 9 · Answer 3 · answered Jun 22 '12 at 10:10

As Ivan explains, there are no official Sunacle jars in Maven. However, it is quite often the case that an implementer of a given API will publish an artifact for that API (the API itself, rather than their implementation of it.

In the case of JPA 2.0, Hibernate publish org.hibernate.javax.persistence:hibernate-jpa-2.0-api, which contains just the javax.persistence classes, and no Hibernate-specific stuff.

My build.gradle therefore says:

dependencies {
    compile group: 'org.hibernate.javax.persistence', name: 'hibernate-jpa-2.0-api', version: '1.0.1.Final'
    runtime group: 'org.hibernate', name: 'hibernate-entitymanager', version: '4.1.4.Final'
}

Which puts Hibernate's release of the API on the compile classpath, and their implementation on the runtime classpath.

Every major provider seems to have their own `javax.persistence` classes. Which is just stupid as you'd think there would be one by 2016 that is the canonical one for JPA 2.0, 2.1, etc... — Powerlord, May 11 '16 at 21:43

score 2 · Answer 4 · answered Apr 28 '12 at 18:12

The direct answer to your questions is: No, it's not possible. The longer version is given here: Apache > Maven > Guide to Coping with Sun JARs . A short summary of the longer answer:

There are (at least) two problems with publishing Sun/Oracle artifacts in central repository:

Restrictive license
Naming convention

JPA 2.0 API maven artifact

4 Answers4

Linked