You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "fabrizio giustina (JIRA)" <ji...@apache.org> on 2006/04/15 17:27:00 UTC
[jira] Created: (JCR-402) release module jackrabbit-bdb 1.0
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
[jira] Closed: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-402?page=all ]
Stefan Guggisberg closed JCR-402:
---------------------------------
Resolution: Won't Fix
cleaning up "Open Issues" list
> 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
[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Alexandru Popescu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12375172 ]
Alexandru Popescu 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.
./alex
--
.w( the_mindstorm )p.
> 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
[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Tom Duffey (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12436370 ]
Tom Duffey commented on JCR-402:
--------------------------------
"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."
So, where can I find this now that it has been removed?
> release module jackrabbit-bdb 1.0
> ---------------------------------
>
> Key: JCR-402
> URL: http://issues.apache.org/jira/browse/JCR-402
> Project: Jackrabbit
> Issue Type: Wish
> Components: contrib PMs
> Affects 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
[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Alexandru Popescu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12374660 ]
Alexandru Popescu commented on JCR-402:
---------------------------------------
I added my vote for it (I'm one of those users :-) ).
./alex
--
.w( the_mindstorm )p.
> 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
[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12375153 ]
Jukka Zitting commented on JCR-402:
-----------------------------------
AFAIK we can't release the BerkeleyDB persistence manager as the BerkeleyDB license is incompatible with ASLv2. Please enlighten me if I'm wrong.
> 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
[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12436686 ]
Jukka Zitting commented on JCR-402:
-----------------------------------
> So, where can I find this now that it has been removed?
It's still available in the contrib folder.
> release module jackrabbit-bdb 1.0
> ---------------------------------
>
> Key: JCR-402
> URL: http://issues.apache.org/jira/browse/JCR-402
> Project: Jackrabbit
> Issue Type: Wish
> Components: contrib PMs
> Affects 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