aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giuseppe Gerla (JIRA)" <>
Subject [jira] [Commented] (ARIES-1649) Aries EclipseLink Adapter packaging issues
Date Thu, 05 Jan 2017 08:56:58 GMT


Giuseppe Gerla commented on ARIES-1649:

> The version of EclipseLink used should then not be upgraded over time unless explicitly

Ok, this is clear

> This usage is explicitly allowed by the OSGi core specification (R6) in chapter 8 subsection

Yes, I know. But adding 

Require-Capability: osgi.identity; effective:=active; filter:="(osgi.identity=org.eclipse.persistence.jpa)"

I receive the following error during compilation

[ERROR] Bundle org.apache.aries.jpa:org.apache.aries.jpa.eclipselink.adapter:bundle:2.6.0-SNAPSHOT
: osgi.wiring.* namespaces must not be specified with generic requirements/capabilities

> Aries EclipseLink Adapter packaging issues
> ------------------------------------------
>                 Key: ARIES-1649
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Timothy Ward
>            Assignee: Christian Schneider
> 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

View raw message