We can't use LGPL in Apache products we deliver for third party libraries, it isn't allowed.
You can look the following links for more informations about licenses: http://www.apache.org/legal/resolved.html http://www.apache.org/legal/3party.html#criteriaandcategories Emmanuel On Thu, Sep 11, 2008 at 8:12 PM, Ken Liu <[EMAIL PROTECTED]> wrote: > Thanks for the info. > > I read an old email thread (from the 2.0 planning earlier this year) > discussing which JPA provider to use. Was there ever a consensus reached on > this? > > I think Hibernate is probably the most commonly used JPA provider (I use it > in my workplace as well), but there was mention of TopLink Essentials. > Someone mentioned something about the Hibernate license (LGPL 2.1) not > being > compatible with Apache licensing? > > Ken > > On Thu, Sep 11, 2008 at 11:28 AM, Emmanuel Venisse < > [EMAIL PROTECTED]> wrote: > > > Both was "test" branches. If you want to look at one, I'd prefer you look > > at > > mine (continuum-jpa-evenisse) ;-) > > My branch was based on jpa annotations and the other one was done with > sql > > in the code. I think annotations are better but I'm not a JPA expert. > > > > We don't have for the moment a real development on JPA but it is > something > > I'd like in a future version. > > > > Now in trunk, the store is split to few DAO. If you want to propose > > something, I think it would be better to start from scratch on trunk by > > rewriting the continuum-store module. Maybe some other parts will be > > impacted. > > > > Emmanuel > > > > On Thu, Sep 11, 2008 at 4:53 PM, Ken Liu <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > I am interested in contributing to the JPA refactoring effort as I have > > JPA > > > expertise. I saw that there are two jpa branches (continuum-jpa and > > > continuum-jpa-evenisse). Are both of these branches under development? > > Are > > > they both considered to be candidates for merging into the trunk? > > > > > > Any background information on these would be appreciated. > > > > > > Thanks, > > > > > > Ken > > > > > >
