jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Date Wed, 19 Apr 2006 20:24:34 GMT
    [ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12375195 ] 

Jukka Zitting commented on JCR-402:
-----------------------------------

> I am far from understanding this legal stuff, but I am reading the above: "we cannot
release it. If you want it,
> just go in, build it for yourself, and that's it." Is this the way I should read it?
:-S. 

Somewhat, yes. The BerkeleyDB license allows redistribution only with full sources, which
causes the license incompatibility. We can't release the persistence manager because due to
the dependency it could not be used in another product without releasing the source or paying
SleepyCat (or Oracle nowadays).

Even the situation of the source code is a bit troublesome. As a user there is nothing stopping
you from just downloading, building, and using the code, but the problem appears if you want
to include the code or the compiled artifacts in another project.

It should be safe to take any ASF code and use it in a commercial project, but the BerkeleyDB
persistence manager doesn't live up to this requirement. In addition we shouldn't have code
in SVN that we don't plan to release at some point of time. Thus it would actually be good
if the BerkeleyDB persistence manager was moved to an independent project somewhere else.
We could still link to it on the web site as a related add-on project, and it could be released
independently.

> release module jackrabbit-bdb 1.0
> ---------------------------------
>
>          Key: JCR-402
>          URL: http://issues.apache.org/jira/browse/JCR-402
>      Project: Jackrabbit
>         Type: Wish

>   Components: contrib PMs
>     Versions: 1.0
>     Reporter: fabrizio giustina

>
> The berkeydb persistence manager in contrib is stable and has been used successfully
by several users.
> It may worth an official release, after committing the two trivial fixes in:
>  JCR-298 missing blob remove
>  JCR-401 update berkeydb version in project.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message