You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Albert Lee (JIRA)" <ji...@apache.org> on 2013/11/11 18:06:18 UTC

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

Albert Lee created ARIES-1134:
---------------------------------

             Summary: 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


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)