I agree with you, Jean-Louis. I have been working with OpenEjb3.2 on another project for some time now, and the "runtime" seems to be pretty stable. I know that we have this little problem with the "CdiScanner.java" code, and that we need to fix the build to pass the tests, but still I think that pushing the 3.2-alpha1 is a good idea. Also, we can have some feedback from the users about the 3.2 version. +1
[]s, Thiago. On Wed, Mar 2, 2011 at 8:06 AM, Jean-Louis MONTEIRO <[email protected]>wrote: > Finally, i'm not in favour of merging JPA 2 changes in 3.1.x branch. > > I would prefer to keep our 3.1.x branch Java EE 5 compatible. > So instead of merging JPA 2 to 3.1.x branch, > > I would prefer to push a 3.2-alpha1 just after JPA 2 support and before > refactoring. > > WDYT? > > Otherwise, it will be a nightmare to maintain ... > > Jean-Louis > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/3-1-4-JPA-2-0-tp3331062p3331464.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com. >
