[
https://issues.apache.org/jira/browse/ARIES-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821691#comment-13821691
]
Albert Lee commented on ARIES-1134:
-----------------------------------
Tim,
Thank you for the explanation and now I got the bigger picture.
I am in the same boat that I need the "cosmic" version change for my current
project but without deeper knowledge and experience of the Aries project and
resources, I am very reluctant committing to do this work now. I also know
eventually, in the next 3-6 months time frame, we have to tackle this piece of
work one way or the other.
To follow the spirit of Agile development process, would It be acceptable to
you we use this JIRA to piece-wide commit code gradually to fully enable the
JPA 2.1 spec in Aries.
* version enabllement
* identify what JPA 2.1 API to use; it looks like Hibernate is the only vendor
has JPA 2.1 API in the maven repository. I have not see any from the Geronimo
project yet.
* code update for compiling against the new 2.1 API
* upgrade the descriptor parser to handle 2.1 xsd
* writing more test to validate 2.1 features
* ... etc ...
I understand this is not the ideal solution but at least a step-wise plan to
meet the goals of all the interested parties.
Thanks for listening.
> 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
>
>
> 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)
