aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giuseppe Gerla (JIRA)" <>
Subject [jira] [Commented] (ARIES-1251) Support jpa 2.0 and 2.1 with the same code base
Date Mon, 06 Oct 2014 13:39:34 GMT


Giuseppe Gerla commented on ARIES-1251:

thanks for your commit.
Previous problem is solved but now I have

[ERROR] Failed to execute goal on project org.apache.aries.jpa.container.itest:Could not resolve
dependencies for project org.apache.aries.jpa:org.apache.aries.jpa.container.itest:jar:1.0.1-SNAPSHOT:
The following artifacts could not be resolved: org.apache.aries.jpa:org.apache.aries.jpa.container.context:jar:1.0.3-SNAPSHOT,
org.apache.aries.jpa:org.apache.aries.jpa.blueprint.aries:jar:1.0.3-SNAPSHOT: Failure to find
org.apache.aries.jpa:org.apache.aries.jpa.container.context:jar:1.0.3-SNAPSHOT in
was cached in the local repository, resolution will not be reattempted until the update interval
of codehaus.snapshots has elapsed or updates are forced -> [Help 1]

About the additional test for JPA 2.1, my code is already aligned with aries trunk. To finalize
my work I need your support because I'm not able to configure JTA in eclipselink.

> Support jpa 2.0 and 2.1 with the same code base
> -----------------------------------------------
>                 Key: ARIES-1251
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: JPA
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
> We currently have two separate code bases for jpa 2.0 and 2.1 support. This is very difficult
to manage when we do source code changes.
> So I will try to create one code that supports both jpa 2.0 and 2.1 by using Dynamic
Proxies where we implement EntityManager or EntityManagerFactory. 

This message was sent by Atlassian JIRA

View raw message