lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] Commented: (LUCENE-1845) if the build fails to download JARs for contrib/db, just skip its tests
Date Wed, 26 Aug 2009 08:39:59 GMT


Simon Willnauer commented on LUCENE-1845:

I added the short discussion I had on legal-discuss for the record.
One person confirmed that we could add the jar to SVN if we do not redistribute them. I'm
not a license guy but I guess we should first figure out what license this particular jar
has. It is not a download from the oracle page (you can only get the sources for this particular
jar not the binary as a download) but something from
without any license notice.

I would suggest to try to build the jar from source with the latest release on the oracle
page so we can be sure about the license. Once I have done this I will send another request
to legal to confirm tha we are not violating anything.

The discussion from legal-discuss
> Hey there,
> We (lucene) have a contrib project that provides a Index-Directory
> implementation based on BerkleyDB. This code downloads a jar file from
> to build and test the code.
> This jar-file is not included in any distribution and we do not plan
> to do so. The problem is that the download site is down very
> frequently so we are looking for another way to obtain the jar. Here
> is the question do we violate the license if we add the jar-file to
> the svn repository but not distributing it at all? Another way would
> be to add the jar to a commiter page on and download
> it from there.
> The license is here:

Complicated matter.
BDB seems viral in that anything that uses must be made available in
source form. So, ASF has no problem fulfilling that requirement, but
downstream users may. OTOH, you say that the BDB is only used to build
(do you really need it to build?) and test your implementation, BUT
you say that you have an implementation based on BDB, so I presume
that it requires it to run.

My interpretation is;
 * IFF your component is purely optional, having a dependency on BDB
is Ok, provided it is not shipped with the release and that the user
is provided with the information that the BDB needs to be downloaded
separately and advised to review their license.

For your second part; Can you stick the BDB jar(s) somewhere more
reliably available?
 * Yes, I think so. The license allows distribution in any form,
source or binary... So, I suggest that you upload it to a dependable
host, such as SF, or similar. --> I
wouldn't recommend it. ASF SVN --> yes, that should be Ok, but there
is a strong recommendation of not putting JARs in there... Also there
is a risk that the encumbrance around BDB is forgotten and used beyond
what is acceptable if it is 'laying around'.


> if the build fails to download JARs for contrib/db, just skip its tests
> -----------------------------------------------------------------------
>                 Key: LUCENE-1845
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Simon Willnauer
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1845.patch, LUCENE-1845.txt, LUCENE-1845.txt, LUCENE-1845.txt,
> Every so often our nightly build fails because contrib/db is unable to download the necessary
BDB JARs from  I think in such cases we should simply
skip contrib/db's tests, if it's the nightly build that's running, since it's a false positive

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message