[jira] [Commented] (ARIES-1134) Enable JPA 2.1 API and correct inconsistent versioning

["Brett E. Meyer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841680#comment-13841680 ] 

Brett E. Meyer commented on ARIES-1134:
---------------------------------------

Does this  partially duplicate ARIES-1047 and https://github.com/apache/aries/pull/3 ?

> 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
>            Priority: Minor
>         Attachments: ARIES-1134.patch, 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.1#6144)