FWIW, specific adapter implementations in Abdera will always be
optional, so that part, at least, is covered. Also, the ant build can
be made conditional on whether hibernate is in the classpath rather than
automatically downloading it and/or we can use a switch similar to the
abdera_xmlsecurity and abdera_spring env variables used to
enable/disable those. For problematic things like hibernate, I would
not necessarily want the Ant or maven builds to automatically download
those jars.
- James
David Calavera wrote:
Oh, thank you Garret. I didn't think on the license terms.
I just thought it could be
interesting that abdera included several orm adapters.
Anyway I'm going to send my code to the abdera
dev mailing list in case of could be useful to someone and I'm going
to follow the legal-discuss mailing list.
Regards
On 2/15/08, Garrett Rooney <[EMAIL PROTECTED]> wrote:
On Fri, Feb 15, 2008 at 4:41 AM, David Calavera
<[EMAIL PROTECTED]> wrote:
Hi,
I've almost finished my hibernate adapter implementation but I've found
a
problem with the hibernate dependencies. The JTA library has a sun
binary
license and it's only available in their web. So, it's mandatory to
accept
the license and I can't download the jar with ant or maven directly.
Due
this issue my tests don't work automatically.
FWIW, Hibernate in general has a host of issues at the ASF due to its
LGPL license, and that's even before you run into the problem you're
hitting here. At the very least we can't ship any LGPL jars with our
releases, and any code that depends on Hibernate has to be totally
optional. This kind of thing is one of those issues that comes up
every so often, and there's currently an ongoing debate about how to
handle it on the legal and board mailing lists.
So anyway, whatever you end up doing you need to be sure to run it by
the legal-discuss mailing list, to make sure it's acceptable.
-garrett
