aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARIES-1649) Aries EclipseLink Adapter packaging issues
Date Wed, 04 Jan 2017 11:21:58 GMT
Timothy Ward created ARIES-1649:
-----------------------------------

             Summary: Aries EclipseLink Adapter packaging issues
                 Key: ARIES-1649
                 URL: https://issues.apache.org/jira/browse/ARIES-1649
             Project: Aries
          Issue Type: Bug
            Reporter: Timothy Ward


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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message