Heads up: Replacing Aries jpa impl for next major version

[Christian Schneider <ch...@die-schneider.net>]

I have almost finished the preparation of the new aries jpa module for 
inclusion into the Apache Aries trunk.

The code is reasonable complete and all current tests pass.
I have also run the OSGi tck for jpa against the current aries jpa code 
as well as against the new code.
In the current code we have a lot of test failures the new code 
completely passes all tests now.

I have slimmed down the api for the new code as much as possible. 
Basically there is just the EmSupplier, JpaTemplate and some necessary 
classes for it.

See: https://github.com/cschneider/jpa-experiments

The project structure like groupIds, artifactIds and package names 
conforms to aries conventions. The aries parent pom is used.
What is left is to convert the current itests as far as possible to show 
that the new code provides the current functionality.

If you can spare some time I would be happy about any feedback.
I plan to create a 1.x branch for the current aries jpa code and put the 
new code on trunk on monday.

Christian

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: Heads up: Replacing Aries jpa impl for next major version

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Christian,

good work. It looks good to me.

Regards
JB

On 05/08/2015 04:04 PM, Christian Schneider wrote:
> I have almost finished the preparation of the new aries jpa module for
> inclusion into the Apache Aries trunk.
>
> The code is reasonable complete and all current tests pass.
> I have also run the OSGi tck for jpa against the current aries jpa code
> as well as against the new code.
> In the current code we have a lot of test failures the new code
> completely passes all tests now.
>
> I have slimmed down the api for the new code as much as possible.
> Basically there is just the EmSupplier, JpaTemplate and some necessary
> classes for it.
>
> See: https://github.com/cschneider/jpa-experiments
>
> The project structure like groupIds, artifactIds and package names
> conforms to aries conventions. The aries parent pom is used.
> What is left is to convert the current itests as far as possible to show
> that the new code provides the current functionality.
>
> If you can spare some time I would be happy about any feedback.
> I plan to create a 1.x branch for the current aries jpa code and put the
> new code on trunk on monday.
>
> Christian
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com