[ARIES-1649] Aries EclipseLink Adapter packaging issues

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: jpa-2.6.0
• Assignee: Giuseppe Gerla
• Reporter: Timothy James Ward
• Created: 04/Jan/17 11:21
• Updated: 06/Jan/17 15:41
• Resolved: 06/Jan/17 15:41

Description

The Aries EclipseLink Adapter has two main problems:

1. The package import ranges for the EclipseLink API are overly specific. The latest release of the adapter only works with EclipseLink 2.6, even though all of the APIs it uses were defined long before. This bundle should be built against an older EclipseLink to ensure that Aries JPA doesn't force users to upgrade EclipseLink unnecessarily.

2. The Aries EclipseLink Adapter has no dependency on the EclipseLink JPA bundle. All of the API that it uses comes from EclipseLink Core, and therefore when doing a provisioning resolve operation EclipseLink JPA is not added! This needs to be fixed with a Require-Capability for EclipseLink JPA. Require-Capability: osgi.identity;filter:='(osgi.identity=org.eclipse.persistence.jpa)';effective:=active