Hi Jean-Louis, I'm still working on that... I was having trouble getting the maven to run. For some odd reason it does not download all the dependencies from the repository, and sometimes it downloads corrupted data. I need to download those manually... rrrrrrrrrrrr! I had some issues with my IDE too... Actually I've just switched to another IDE... Im much happier now...:O) It seems that I'm back on track.
>From your last email, I chose to go with your second option: use javaee-api-6 instead of javaee-api-5. It turns out that this solution is the easiest one. In order to use it, I needed to implement some jee6 new methods, but these new methods are simply throwing a "not implemented" exception. I didn't see any side effects. All the tests are passing. Now, I'm trying to get my personal project running with this new openejb version (currently it uses the trunk version). That includes changing the target to 1.6, removing the ejb31-api-experimental dependency and completing the tests with JPA2. I think that middle April is a fair deadline for it. Actually, I think I can finish it before that, but let set this date for safety... :O) tkx, Thiago. On Fri, Mar 18, 2011 at 6:31 AM, Jean-Louis MONTEIRO <[email protected]>wrote: > Hi Thiago, > > I saw some commits regarding JPA 2 support in 3.2 branch. > Could you provide a short status about where you are? > > I really would like to push a 3.2 based on 3.1 code base and supporting JPA > 2. > > Thanks > Jean-Louis > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/3-1-4-JPA-2-0-tp3331062p3386699.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com. >
