Db4o

[Bjarte Stien Karlsen]

Hello List,

I was just curious if there will be any support for using db4o
(db4o.com) in the model layer of Lift.

--
regards
Bjarte Stien Karlsen

[David Pollak]

On Dec 9, 2007, at 1:01 PM, Bjarte Stien Karlsen wrote:

>
> Hello List,
>
> I was just curious if there will be any support for using db4o
> (db4o.com) in the model layer of Lift.

It's an interesting concept, but it can't be done as part of lift as
(oh no, here I go again), DB4O is GPL and the GPL and Apache 2.0
licenses don't mix.

If there was a way to license db4o in such a way so as to not trigger
this problem, I think it'd be a great thing to add to lift (I'd use
it in a heartbeat.)

>
> --
> regards
> Bjarte Stien Karlsen
> >

--
David Pollak
http://blog.lostlake.org

[David Bernard]

But it's possible to create a plugin. It won't be part of lift, but it could be distributed separetly, and end-developper could mixe both (in accordance to licenses).

To answer your request, From my knowledge there is no project about db4o + lift. You could start it ;).

Regards

/davidB

[David Pollak]

I've got a ping out to the DB4O folks to see if there's something
that can be done.

[Chris Baker]

On Dec 9, 2007 4:08 PM, David Pollak <d...@athena.com> wrote:

It's an interesting concept, but it can't be done as part of lift as
(oh no, here I go again), DB4O is GPL and the GPL and Apache 2.0
licenses don't mix.

This might be of interest:

db4o News and Press Releases

db4objects Introduces New Licensing Option to Extend Open Source Compatibility

New dOCL license fosters rapid adoption of db4o in wider range of open source projects

SAN MATEO, Calif., Jan. 24, 2007 - db4objects (www.db4o.com), creator of the leading open source object database, today announced the introduction of a third licensing option dubbed dOCL (db4o Opensource Compatibility License). The licensing option supports free/open source projects that want to embed db4o under standard open source licensing terms other than GPL.

This announcement broadens db4o's adoption for projects licensed under Apache, LGPL, BSD, EPL, and other standard open source licensing terms. Major open source projects that currently include or that plan to include db4o are Novell's Mono, Redhat's Fedora-Linux, Eclipse (Apogee), Spring, JPOX, Apache-Lucene (Gdata) and Funambol (SyncML).

Chris

[David Pollak]

Chris,

Chatting with their CEO right now.

The issue is not just the lift issue... it's the apps built with lift issue.

As DavidB pointed out, it's cool to do a plugin for lift as long as it's not distributed with the core lift release.

The problem comes when the code lift release contains GPL code or links to GPL code... it means that all code that's built with lift must conform to the GPL's requirements.

Imagine if someone wants to build a non-open source app (e.g., Much4) on top of lift.  Even if the app is not using db4o, there's a license conflict because lift "links to" db4o and that imparts the requirements of the GPL on the code that links to lift because it can very easily and reasonably be argued that the linking is transitory.

So... without poking the GPL bear thing again... that's the issue.

I want to find a way around the issue so we can have db4o support and allow people who actually use db4o in their apps either license it or open source their apps.

Thanks,

David