| Summary: | Publish official Maven JPA API 2.x & later jars | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Matthew Adams <matthew> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | maven | ||
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
Build Identifier: 2.0 It's always been difficult to use JPA in Maven or Ivy because there's no official JPA 2.0 jar that's published. People have to end up using <dependency> <groupId>org.eclipse.persistence</groupId> <artifactId>javax.persistence</artifactId> <version>2.0.0</version> </dependency> or <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.persistence</artifactId> <version>10.0-b28</version> </dependency> or <dependency> <groupId>org.glassfish.persistence</groupId> <artifactId>persistence</artifactId> <version>10.0-b28</version> <packaging>pom</packaging> </dependency> or <dependency> <groupId>org.apache.geronimo.specs</groupId> <artifactId>geronimo-jpa_2.0_spec</artifactId> <version>1.1</version> <packaging>bundle</packaging> </dependency> or others (Hibernate?). Also, there does exist <dependency> <groupId>javax.persistence</groupId> <artifactId>persistence-api</artifactId> <version>1.0.2</version> </dependency> in Maven central. Please publish a Maven artifact for JPA 2.0 & subsequent releases with groupId "javax.persistence" and artifactId "persistence-api" so that it behaves like JPA 1.0.2. Reproducible: Always Steps to Reproduce: (enhancement request)