aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (ARIES-1134) Enable JPA 2.1 API and correct inconsistent <aries.osgi.import> versioning
Date Tue, 15 Jul 2014 13:13:05 GMT

     [ https://issues.apache.org/jira/browse/ARIES-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jean-Baptiste Onofré resolved ARIES-1134.
-----------------------------------------

    Resolution: Duplicate

> Enable JPA 2.1 API and correct inconsistent <aries.osgi.import> versioning
> --------------------------------------------------------------------------
>
>                 Key: ARIES-1134
>                 URL: https://issues.apache.org/jira/browse/ARIES-1134
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint, JPA
>            Reporter: Albert Lee
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>         Attachments: ARIES-1134.patch
>
>
> There are some inconsistency of <aries.osgi.import> version useage between these
modules:
> jpa/jpa-api/pom.xml
> jpa/jpa-container/pom.xml
> jpa/jpa-container-context/pom.xml
> jpa/jpa-container-eclipselink-adapter/pom.xml
>             javax.persistence;version="[1.0.0,2.1.0)",
>             javax.persistence.spi;version="[1.0.0,2.1.0)",
>             javax.persistence.criteria;version="[1.1.0,2.1.0)";
>             javax.persistence.metamodel;version="[1.1.0,2.1.0)";
> and 
> jpa-blueprint-aries/pom.xml
>             javax.persistence;version="[1.0.0,3.0.0)",
> I would like to propose all these modules' version updated to 
>             javax.persistence;version="[1.0.0,3.0.0)",
> so the JPA 2.1 API can be used at runtime, if enabled by the container environment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message